Should Gutenberg Stay a Plugin, or Is It the Future of the WordPress Ecosystem?
WordPress is promoting Gutenberg as the future of site building, but is it really? Find out why many believe the block editor should stay a separate plugin instead of being built into WordPress core.
A Divisive Change in WordPress: Introduction
WordPress 5.0 came out in 2018 and added Gutenberg, the block editor, to the core. Instead of giving users the option to choose, WordPress replaced the Classic Editor entirely.
Since then, the arguments have only gotten louder: Is Gutenberg the future of WordPress, or should it have stayed a plugin like BuddyPress or WooCommerce?
Why Gutenberg Supporters Want It in Core
Supporters say Gutenberg:
Makes editing more modern with blocks.
Produces cleaner code than most page builders.
Lays the foundation for Full Site Editing (FSE).
For those who want WordPress to compete with Wix or Squarespace, Gutenberg seems like a natural step forward.
Keyword Target: What is the Gutenberg block editor in WordPress core
The Case Against Gutenberg in Core
Not Everyone Wanted It
Many site owners preferred the Classic Editor. Forcing Gutenberg into core — then requiring a plugin to disable it — felt backwards.
Plugin vs. Core Philosophy
WordPress has always thrived on a “lean core, extend with plugins” philosophy:
Want e-commerce? Install WooCommerce.
Want forums? Add bbPress.
Need membership tools? Use a plugin.
So why wasn’t Gutenberg treated the same way? Putting it in core went against WordPress tradition.
Frustrations for Developers and Users
Developers now need to learn React just to make simple blocks.
Many plugins broke when Gutenberg launched.
Agencies struggle because the UI changes frequently.
Keyword Target: Downsides of the Gutenberg block editor
Problems with the Ecosystem
Agencies relying on Elementor, Divi, and Beaver Builder pushed back.
Users are split between Classic Editor and Gutenberg.
Block themes created confusion compared to traditional themes.
Should Gutenberg Have Been a Separate Plugin?
The strongest argument is that Gutenberg should have followed the plugin-first model:
It could have gained adoption naturally.
The community would have chosen it based on merit.
Competing editors could still thrive, giving users choice.
This mirrors WordPress’s historical success: freedom through flexibility.
The Future of WordPress: Break Up or Come Together?
WordPress leadership is fully invested in Gutenberg. Full Site Editing and block themes are expanding rapidly.
But the risks remain:
Too much change could drive users to other platforms.
Agencies may double down on third-party page builders.
Developers may resist a JavaScript-first environment.
Conclusion: The Future Is Still Up in the Air
Is Gutenberg the next big thing for WordPress? Maybe — but not for everyone.
Had Gutenberg grown as a plugin-first ecosystem, adoption might have been smoother. Forcing it into core risks breaking WordPress’s tradition of flexibility and user choice.
The future of WordPress may not be “Gutenberg or nothing,” but an ecosystem where Gutenberg is just one of many options.
FAQ (SEO-Friendly)
FAQ Accordion / Toggle (use Elementor Accordion widget):
Q1: Is it still possible to use the Classic Editor in WordPress?
Yes — the Classic Editor plugin brings back the old interface and is supported until at least 2026.Q2: Does Gutenberg make WordPress SEO better?
In some cases, yes. It produces cleaner code than many page builders, but it doesn’t guarantee higher rankings.Q3: Will Gutenberg replace page builders?
Not likely. Page builders like Elementor still dominate for advanced design and flexibility.
