WordPress Gutenberg editor is rolling out as the default for entering content. It’s a new paradigm for content creation that’s not ready for prime time.
WordPress Gutenberg Editor Not Ready for Prime Time
I have recently tried the WordPress Gutenberg Editor and found it is not ready for prime time. The interface is not at all intuitive. For the near future, I am sticking with Fusion builder or Beaver Builder for my drag and drop editor. I will try Gutenberg again in 6 months. But I am not sure that it is going to get the user adoption that will compete with SquareSpace or Wix.
It looks like WordPress is going full speed ahead with Gutenberg as the default for WordPress 5.0, but will offer a “Classic Editor” plugin that will disable Gutenberg as the default entry mode.
- It generates verbose HTML with excessive wrapper <div> tags and comments (e.g., <!– wp:block –>), which can bloat page code, slow load times, and complicate front-end styling. It’s a highly idiosyncratic and non-standard approach that hides semantics in comments.
- It is now the default and you must remember to select “Classic Editor” to edit a page, you cannot assign a page a default setting of “classic.”
Update March 2025: accurate data is hard to come by but most estimates place Gutenberg adoption at 10-20% of all WordPress sites 7 years in. It would have been better to offer it as a no cost option but not jam it in as a default. We use it on less than 1% of the pages on this site.