Whether you are a WordPress user, developer or someone like me who seems to come up with an idea and build a new website every week, you are familiar with the Great WordPress Update of 2018. WordPress introduced Gutenberg, with a long list of new functionality and features.

The list of new features includes content blocks, dynamic content, better table creation, and many others… But if you have used third-party page builders or plugins that interact with the WYSIWYG (what you see is what you get) you probably noticed that things were broken after the core update was applied and Gutenberg was implemented on your site. Worse than that if you have deployed or manage sites for end users and they contribute you probably got a lot of emails and phone calls asking why their “site was broken”.

Plugins have started adapting and updating so that they can work with Gutenberg’s new editor, but for the most part, a lot of WordPress devs and users were SOL.

The result?

Over 3 million WordPress users have rejected using Gutenberg’s new editor and installed a plugin (provided by WordPress after they realized just how much of an impact this was having on the users of the CMS) called “Classic Editor”. You install this plugin and your WordPress editing experience goes back to pre-Gutenberg and generally all is well again.

wordpress gutenberg classic editor

What this tells us, in my opinion, is that the users of WordPress, and the WordPress development community wasn’t quite ready to embark on this journey with Gutenberg just yet.

While the functionality they introduced does appear to be fantastic, it has a long way to go before users are utilizing it.