Forcing Gutenberg on users? Bad idea.
-
A visual editor could’ve been a good thing if the intention was to ship it alongside the classic editor.
But gutenberg is invasive, and the talk of removing key features that made WordPress powerful is shameful.Key aspects of WordPress success are backwards compatibility and the fact that it’s extremely simple so a solution to most content problem can be built upon it easily.
Instead gutenberg forces a specific workflow on the users, a specific way of treating content, and it basically destroys a good deal of good plugins and features.
I have 10 websites made in wp right now, and none of them will benefit from gutenberg. In fact if this get integrated into the core, it will be a source of problems, despite the fact that I always followed good development practices and not never did any non-standard thing, nor I ever used a plugin that pollutes content with non-stardard things.
Well, I know this is not a situation where users are listened, so I’ll just voice my discontent and wait. If I’m wrong, I’ll get a new powerful editor. If I’m right, I can say “I told you so”. Feels good not having to decide the destiny of the most used tool for creating websites.
The topic ‘Forcing Gutenberg on users? Bad idea.’ is closed to new replies.