Great But Must Be in Opt For Developers .
-
First of all, i have to thank all the developers that worked hard to this huge and great improvement in wordpress which is Gutenberg. I tried to use it and understand what are it’s pros and cons, and finally i found it very helpful, flexible and easy to use, and also i recognized some features missed with the Gutenberg editor, just like the Custom Media Buttons which is neccesary and useful for developers to make things happen fast and easy . I must say and tell you as wordpress core developers to not force users and developers to use Gutenberg as main and the only editor in the platform, i suggest let it in opt for developers and also leave it as plugin .
-
Technically both the current editor and Gutenberg can exist in core. Gutenberg is just a REACT override of the current editor. The Classic Editor, if activated, prevents this override therefore suggesting that the same thing could be incorporated completely in core with a toggle on/off in Reading settings.
I see and get why those who are able to work with it are having a frictionless experience with it as it fits with their workflow and use case of placing content into a post one block after another. At the same time it removes a lot of the functionality that is catered for in the current editor and this is not just about content creation. A lot of other functionality is happening in that interface. It’s not all about the the content area.
In a addition some obvious improvements that are long called for in the current editor are not being tackled by Gutenberg, namely bringing a better editing experience to the text tab in TinyMCE (or its replacement) in the form of a proper IDE interface with respect for indentation, code hinting, colour coding for syntax, dark mode and respect for indentation of the coed block. On the other end of the spectrum, a structure system for page layout: sections/rows/columns, grid, flex or, whatever you are having yourself. This would be a basic foundation with an API for page builders to integrate with. This would solve the sticky task of dealing with changing themes/builders or turning them of altogether and the need not to have shortcodes as is the case with some of the builders.
It’s surprising why the Gutenberg (classic if you want, plugin) editor choice is being implemented in this way. I think the Gutenberg concept would get a better reception if it wasn’t been touted as the de-facto default editor with a big question mark left over the current editor. As it is, the approach has left a lot of people confused and angry. They could have opted to showcase Gutenberg as the editor in TwentyEighteen and other themes that are developing in that direction. This would have allowed for a narrower but better implementation of features that best show Gutenberg’s potential instead of the scrabble to implement everything for a big waterfall release where issues arise.
The future landscape looks uncertain for developers and users who want and need to still use the current editor with no copper-fast guarantees of how long it will be around for. We don’t know if and when the current (Classic) editor will be ripped out altogether.
It’s the kind of environment where schisms are unavoidable.
The topic ‘Great But Must Be in Opt For Developers .’ is closed to new replies.
