*Install Classic Editor, to bypass this rubbish
Thanks for your feedback! Can you elaborate on what you found confusing about Gutenberg? We’d love to be able to work to address these issues and make it more helpful for your workflow. 🙂
Cheers!
Hi, well firstly it is a huge mistake to force this onto people using the default core WordPress setup.. Plugins are and should always be optional, not mandatory!
Then, the next issues caused by this was the instant problems it caused with themes that people were using and the forced learning curve administrators were forced to adapt to, to make simple edits to content.. to the point of it rendering some tasks non functional.
Add to that bug and flaws in its release design, and you have a recipe for a backlash and negative feedback.
How this should have been done would be ‘Promotion’ of the plugin, but always keep it optional. My personal view is that i will NEVER use it, most themes come with things like Visual Bakery etc., if they are using a page builder overlay system anyway, so Gutenberg will always remain a pain in the neck for most WordPress users, even new installs will find the alternative page builders and core builder much easier to use and learn.
