Fun for bloggers, terrible for CMS

If you don’t know you absolutely can still use the Classic Editor through the plugin: https://www.ads-software.com/plugins/classic-editor/. If you add that from now you can ensure even when 5.0 comes, the old editing experience will remain for you. Thanks for taking time to leave a review. What would you feel would mean this worked for non-bloggers?

I’m aware of this plugin and honestly, I think it’s weird that a separate plugin is required for this at all.
Why isn’t this feature in core by the time 5.0 comes out. Why not let admins define whether a post type should be edited in Gutenberg or normal?

Don’t get me wrong, it works nice and looks really good for making long and fancy blog posts.
But not all post types are content/text based pages. Most of the time only posts and pages (WP core types) are.
In most other cases meta/custom fields are used extensively in combination with custom templates that handle the page templates.

I don’t see Gutenberg working nice with anything else than blog-like posts, or in other words, long pages. For simple text input it’s way too bulky (takes up all the room on the page where you would like all other options and fields instantly visible) and for page builder use-cases it’s too basic since you can only edit the part within the actual content of the template, not the whole page.
So in short, other than for blogging (long posts) and basic websites, in my opinion it doesn’t help or contribute to the way users and developers use and create more complex CMS. It will probably only sit in the way..

So, good news!

An admin -can- define if a post type shows up in Gutenberg or not, you may do this using the Gutenberg Ramp plugin.

It’s also worth noting that any custom post type that disables the use of the REST API (show_in_rest) will also use the classic editor fallback. This gives developers the power to “opt-out” of Gutenberg for their special content if they know it’s incompatible at this time.

Still I feel like this should be supported by core to ensure it will stay compatible with new updates. If it’s a plugin it’s always possible that the author is too late with updates for new WP version or it could even be possible that the plugin gets abandoned.
With such a big change in core I think it’s up to core to facilitate such features, not plugins… This makes sure it will always be maintained on new updates.

As for show_in_rest. This feels weird to me as REST has nothing to do with Gutenberg as far as I know.
Why not just add a new option editor (for example) which is set to gutenberg by default.

• This reply was modified 6 years, 3 months ago by Jory Hogeveen.

The reason for the REST setting is because Gutenberg relies on the REST API to fetch data for posts. Adding an option like that makes no sense, as once it is in core it will not be “Gutenberg” any more, it will just be “the WordPress editor”.

We are working really hard to ensure that existing plugins do not break (and very few of them will, they would have to interact directly with the editor to truly do so), and if they do things ill degrade to the classic editor automatically when possible. We do have a big eye on backwards compatibility and understand that there are plugins which may not receive updates etc at this point in time that sites rely on and although we’d love it if they used a supported alternative, we do not plan on leaving them stranded.

@clorith I’m using WordPress as a headless CMS for a React app which fetches the content from WordPress using the WP REST API so using the show_in_rest setting to “opt-out” of Gutenberg is a bad idea.

@keraweb I totally agree with you that Gutenberg is a step in the right direction for bloggers writing blog posts but Gutenberg developers need to understand that a lot of people also use WordPress as a CMS with ACF fields. And the current implementation of custom fields is pretty poor.
Gutenberg will never replace custom fields because saving everything in the post_content field doesn’t work for websites that require structured data.
For example, if you were to build a website like IMDB or GoodReads then Gutenberg will only get in the way.