Please not in core – as plugin only
-
Please do not include Gutenberg as mandatory in Core. Gutenberg does not belong there – it should be offered as an optional plugin only.
Gutenberg is a huge step in a questionable direction. It appeases a few entry-level users at the expense of developer and advanced/power-user preferences. I believe that isn’t a good trade-off, and sends WP in a direction that is inconsistent with the core value propositions and platform methodologies that are leveraged by millions across the globe.
Yes, I know there is a plan to offer a plugin that turns off Gutenberg and re-instates the WP editor, but I implore the WP Team to do the opposite: Gutenberg should be offered optionally as a plugin, not mandatory in core.
-
I agree with the points you make but we need to clarify one thing. The classic plugin doesn’t reinstate the current editor. What it does is turn off the REACT override that is Gutenberg. In fact if you were to create a custom post type with its own custom fields and disable the TinyMCE text area that represents the main content Gutenberg would not be activated at all.
This seems to be the way things are going to work but who knows, at some point the implementation of the current editor could be deprecated.
One of the goals of Gutenberg is to remove what they are calling the mystery meat. One such piece of mystery meat are the shortcodes something that a novice may not understand. But if you look at the many functions of these shortcodes one is to interpolate custom values from custom fields into your content. Not just into your layout but in the middle of a paragraph for example. It seems if you look at it from this point of view, Gutenberg is handing us, the current users, some mystery meat like, how do we now do the things that are possible with the current way WordPress works.
Don’t get me wrong. I see a lot of merit in what has been done with Gutenberg but it is the wrong tool for the jobs we are already doing. It all seems a bit convoluted and given the point I made about it being a REACT override, much like how Divi and other builders override the main content area, it begs the question why you wouldn’t just allow users to switch on or off Gutenberg without having to resort to a plugin.
- The topic ‘Please not in core – as plugin only’ is closed to new replies.
