15 Comments

  1. Ted Magwell

    That quote editor is a great example of how the removal of WYSIWIG simplifies life for everyone. Easier for editors to add content, easier for designers to style it, easier for developers don’t need to maintain.

    Gutenberg tries to be both article editor (Medium) and page builder (Squarespace). I wish it focused on one thing.

    Backend WYSIWYG editor also adds complexity, as developers need to style both frontend and backend.

    Say, a user created an image gallery in Gutenberg, now we want to change the markup of all galleries on the frontend. How we do this? Since Gutenberg doesn’t store gallery attachment IDs in JSON, we have to parse HTML via PHP to retrieve attachment ID from “data-” attribute, which is a horror.

    Now imagine the same gallery editor, but without WYSIWIG part. Where each image is a simple square that can be reordered. Where data is stored in a simple array. It becomes to much easier for everyone.

    Report

    • Bastian

      Now imagine the same gallery editor, but without WYSIWIG part. Where each image is a simple square that can be reordered. Where data is stored in a simple array. It becomes to much easier for everyone.

      Yes, I’d like a non-opinionated gallery field so I could style it as a slider or a carousel or a masonry grid in the frontend.

      Report

  2. Anh Tran

    I’m happy for ACF users and developers. ACF is the most popular plugin for custom fields, and its compatibility is crucial for developers. We’re at Meta Box has done this work months ago when the original plan of releasing Gutenberg was April. I was hoping ACF announced this move earlier because it’s a big concern for developers.

    Report

  3. JeffC

    Game changer, ACF team is awesome.

    Report

  4. Hashim Warren

    Elliott Condon for President.

    Report

  5. Linh Tran

    Great, ACF! Waiting for it so long. Unfortunately, metabox.io is one step ahead. The game is quite interesting now, hah. I moved to use Meta Box in recent projects but now will consider going back with ACF.

    Report

  6. nK

    We really needed the ACF for Gutenberg, so, we created our own plugin for build custom Blocks and Metaboxes – https://wordpress.org/plugins/lazy-blocks/

    Report

  7. Marcus Hiles

    Excited to see how ACF works both with Gutenberg and to improve upon Gutenberg. I manage alot of sites that rely heavily on this plugin.

    Report

  8. Rick Gregory

    Gutenberg is nowhere near ready and shouldn’t be forced into 5.0. It will be, but the idea that the edit screens I’ve created using ACF will be screwed over so that Matt can compete with Wix, et al is infuriated and the team has mismanaged this from the start with some of the worst communications and process (externally visible process at least, e.g. roadmaps and timeline) that I’ve seen.

    Report

    • LABCAT

      Your edit screens are not going to be screwed over though, that is your misconception. Just install the classic editor or Gutenberg ramp plugins and your edit screens will stay as they are.

      Report

      • Jim

        Installing more plugins as a workaround just to keep things functional isn’t a long-term solution though. Gutenberg might be great for certain types of sites but might not be the best experience for others. I’m not a fan of my ACF fields being pushed all the way to the bottom and clients having to hunt/scroll to manage pages – I typically prefer to build my own interfaces with flexible content fields and hide the default TinyMCE editor. It still feels like Gutenberg should be available as a standalone plugin for those that want the builder/drag and drop editing experience, not rolled into core as the default.

        Report

  9. Olivier S

    Guttenberg and the ACF blocks builder is great for editing content. But ACF is not only used by developers for the content of a post but for the settings as well.
    For instance, you could have a related post meta box created with ACF and populating this box is part of the editing process. This is not going to be replaced by a block in the Guttenberg editor.
    Meta boxes are still very needed in order to allow more granular settings, taxonomies, relationships… And it’s a long-term need.

    Report

Comments are closed.

%d bloggers like this: