Gutenberg Block-based editor
-
I just learned that plans are for the ‘classic editor’ to only be supported through 2022. I wanted to let you know that as an experienced IT professional who uses WordPress to manage my personal websites, I consider this to be a fatal step in the wrong direction.
I selected WordPress primarily because its editor (the classic editor) while imperfect, provides the right balance between a WYSIWYG content creation and near-html fine tuning. In short, I can have my cake and eat it to by quickly drafting a page or post, then in most cases, easily switching to code view to apply needed code-level tweaks.
While the new editor has this ability in principle, in practice it’s more a choice between an training-wheel (block-based) editor that is 100% an encumberance and nuisance, and just coding the page in html.
That’s not a choice I can live with, and worse, the new editor buries the toggle between the two editors. Honestly, I just cannot see maintaining a website long term using the new editor, and I suspect that if you look into the number of users who are using the ‘classic editor’ plug-in, you’ll find I’m not alone.
‘Block-based’ editors are like the alphabetically arranges keyboards used on typewriters in the 19th century. They made something inherently complex easier to teach to amateurs, but utterly useless to professionals.
I hope you will re-think this direction.
-
Hi @cstuarthardwick, thank you for the feedback. The classic editor plugin is open source so I’d imagine as long as someone wants to maintain something like it, you’ll have options.
That said, If we could make the newer editor less cumbersome, so you could just write unless you wanted to add a block or change a paragraph, would that help?
Also, if you just switch to the code tab and type there, only switching back to the other view to add formatting, does that help at all?
- The topic ‘Gutenberg Block-based editor’ is closed to new replies.