Steve Morton

@joe I was around before Custom Post Types and I can’t speak for everyone else but I was super excited. I’m excited for Gutenberg too. I think the block approach is fantastic. But I’m also a bit concerned.

Though I would have to ask the question, how many here that are saying Gutenberg is bad for WordPress, go around and install a copy of Advanced Custom Fields, Divi, Beaver Builder or some other content block type creation tool?

I think that is a valid point but I would say that, for most developers, Advanced Custom Fields does not fit with the other two examples.

I use ACF on nearly every project. Gutenberg does not replace the functionality of ACF for me. Gutenberg currently treats ACF and indeed every other meta box as a second class citizen. For many content types and use cases this will be very detrimental for user experience.

Take for example products in an e-commerce store. Products typically do not need a long form content editor – just a simple text box for a short description will do in most cases. The important bits – price, sizes, image gallery, etc – are all the domain of custom fields and meta boxes.

With Gutenberg as it is today you’d have this giant editor taking up the screen with just one paragraph of text and all of the important fields hidden away. Not ideal :-/ Even if you can disable the Gutenberg editor entirely for a given post type what does the resulting edit page look like? If you have two entirely different experiences for users it could be confusing.

Name *

Email *

Website:

Topic Title (Maximum Length: 80):

Forum:
— No forum —AI and WordPress Articles Blocks Showcase Discussions Events Introductions Jobs and Working in WordPress Podcast Episodes Site and Block Editor