It has been over five years since WordPress introduced the block editor (codenamed Gutenberg) in WordPress 5.0, sparking one of the most polarizing debates in the CMS community’s history. Today, Gutenberg is no longer a clumsy plugin trying to find its footing; it is a mature, fully integrated editing experience that forms the foundation of modern Full Site Editing (FSE). Yet, millions of sites still cling tightly to the Classic Editor.
For WordPress developers, agencies, and power users, deciding which editor to standardize on is a critical architectural decision. Is the Classic Editor still a viable tool for professional workflows, or has Gutenberg evolved to the point where ignoring it is a liability? Let us break down the technical realities of both editors in today’s development ecosystem.
The Evolution of Gutenberg: From Content Editor to FSE
When Gutenberg launched, it was criticized for being buggy, unintuitive, and disruptive to established client workflows. Fast forward to today, and the block editor has transformed into a robust visual page builder and templating engine. Built on a modular React framework, Gutenberg introduces concept uniformity: everything—from a simple paragraph to an entire site navigation menu—is a block.
Key Advantages of Gutenberg Today
- Visual Site Building: With Full Site Editing (FSE) and block-based themes, developers can build headers, footers, and templates inside the editor without touching complex PHP files.
- Native Performance: Unlike heavy third-party page builders (such as Elementor or Divi), Gutenberg generates remarkably clean HTML markup, resulting in faster load times and improved Core Web Vitals out of the box.
- Block Patterns and Synced Patterns: You can build, save, and export pre-designed layouts. Synced patterns (formerly Reusable Blocks) allow global content updates from a single source.
From a developer’s perspective, Gutenberg enables the creation of highly curated editing experiences. Using theme.json, you can programmatically restrict color palettes, typography, and layout options, preventing clients from breaking the site’s design system.
The Classic Editor: Why It Refuses to Die
Despite the massive push toward Gutenberg, the Classic Editor plugin remains highly active with millions of installations. TinyMCE, the engine under the hood of the Classic Editor, represents a simpler era of content creation. It is a straightforward, document-centric word processor that does one thing exceptionally well: text entry.
Why Developers and Agencies Still Choose the Classic Editor
- Workflow Speed and Simplicity: For writers producing pure text or simple editorial content, the distraction-free, linear nature of the Classic Editor is often faster and less cumbersome than managing block nesting.
- Legacy Codebases: Many enterprise sites feature highly customized metadata schemas powered by Advanced Custom Fields (ACF). Migrating these complex page-builder setups to blocks can require costly refactoring.
- Predictability and Client Training: Non-technical clients often find the freedom of Gutenberg overwhelming. The Classic Editor acts as a safe, highly restricted sandbox where clients cannot easily alter structural layouts.
If you need to disable Gutenberg selectively on custom post types or legacy templates, you do not always need a plugin. You can manage this programmatically using the use_block_editor_for_post_type filter:
add_filter('use_block_editor_for_post_type', function ($use_block_editor, $post_type) {
// Disable block editor for a custom post type named 'portfolio'
if ($post_type === 'portfolio') {
return false;
}
return $use_block_editor;
}, 10, 2);Gutenberg vs Classic Editor: Technical Comparison
To help you decide which editor is right for your next project, let us compare their core architectural differences side by side.
1. Core Architecture and Extensibility
The Classic Editor relies on TinyMCE APIs and PHP hooks. Modifying the editor experience usually involves adding custom buttons or injecting custom CSS. Gutenberg, on the other hand, is a modern JavaScript application built on React. Extending Gutenberg requires knowledge of JSX, ESNext, Webpack, and the @wordpress/scripts build package.
2. Layout Flexibility
Classic Editor forces you into a single-column container. Any multi-column or complex layout requires shortcodes or custom page templates. Gutenberg provides advanced layout controls natively—columns, grids, groupings, and flexbox settings are accessible directly within the sidebar.
3. Data Storage and Schema
The Classic Editor stores raw HTML directly in the post_content column of the database. Gutenberg also stores standard HTML but utilizes HTML comments to save block parameters and metadata:
This is a Gutenberg block.
While this ensures backward compatibility if the block editor is deactivated, it does introduce a layer of parsed string data that can sometimes make database-wide search-and-replace queries more complex.
The Hybrid Approach: Bridging the Gap
Many modern developers have adopted a hybrid workflow that combines the developer-friendly constraints of the Classic Editor with the layout flexibility of Gutenberg. This is primarily accomplished using ACF Blocks.
Advanced Custom Fields allows you to register custom Gutenberg blocks using standard PHP and CSS templates, bypassing the need for a complex React build setup. This represents the ultimate sweet spot for developers who want to build tailored, block-based sites quickly:
add_action('acf/init', 'register_custom_acf_blocks');
function register_custom_acf_blocks() {
if (function_exists('acf_register_block_type')) {
acf_register_block_type(array(
'name' => 'testimonial-block',
'title' => __('Testimonial'),
'description' => __('A custom testimonial block.'),
'render_template' => 'template-parts/blocks/testimonial.php',
'category' => 'formatting',
'icon' => 'format-quote',
'keywords' => array('testimonial', 'quote'),
));
}
}The Verdict: Which Should You Use Today?
The decision ultimately depends on the scope of your project, your technical stack, and your target users.
Use Gutenberg if:
- You are building a new site from scratch and want to future-proof its codebase.
- You want to maximize front-end loading speed and avoid heavy third-party page builders.
- Your clients need structural design freedom and want to assemble rich, media-heavy landing pages themselves.
Use Classic Editor if:
- You are maintaining a complex enterprise codebase that relies heavily on legacy PHP templates and shortcodes.
- Your content team focuses solely on high-volume, text-only blogging and values visual simplicity.
- You want to lock down the layout completely to prevent clients from misaligning design elements.
As WordPress Core moves closer to fully realizing Phase 3 of its development roadmap (focusing on collaborative editing and real-time workflows), Gutenberg is undoubtedly the future of the platform. Embracing it today ensures your skills—and your sites—remain highly competitive.