The WordPress Block Editor Finally Grew Up

For years, “the block editor” was a polite way of saying “the thing we tolerate while pretending we still prefer the classic editor.” That stopped being true sometime in 2024, and it’s really stopped being true in 2026. The block editor is now the best authoring experience WordPress has ever had, and if you’ve been avoiding it out of habit, it’s worth another look.

What changed

The early block editor felt like a toy bolted onto WordPress. Blocks were clunky, patterns didn’t exist, styles were inconsistent, and power users bounced between “I’ll just use classic” and “I’ll just use a page builder.” Fair reaction at the time.

Then a few quiet years of iteration happened. Patterns arrived and made it possible to reuse whole sections across a site. Full-site editing matured past the “it kind of works” stage. The Style Book in WordPress 6.8 gave you a single place to edit colors, typography, and global styles that cascade through every block. Query Loops got smarter — ignoring sticky posts, showing totals, handling pagination cleanly.

The editor stopped being a block-level tool and became a full layout system. That’s a bigger shift than the release notes make it sound.

What it feels like now

Creating a new page in the block editor in 2026 looks more like building with Notion or Figma than wrestling with shortcodes. You drop in a hero pattern, a features grid, a testimonial row, and a call-to-action — all from a library, all stylable, all responsive out of the box.

Your content team can do this. That’s the important part. They don’t need to open a page builder, they don’t need to wait for a developer, they don’t need to learn Elementor or Divi. They use the editor WordPress ships with, and it’s finally good enough that they don’t want to leave.

Why page builders started feeling heavy

Page builders solved a real problem back when the block editor was weak. They bolted on visual layout tools and gave clients power their WordPress theme didn’t. But they pay for that power in weight — huge JavaScript bundles, bloated DOM, database rows full of builder-specific markup that nothing else can read. A site built on a page builder is usually slower and harder to migrate.

The block editor has quietly closed the capability gap while staying lightweight. A well-built block theme in 2026 ships a fraction of the JavaScript of a comparable page builder site and performs dramatically better on Core Web Vitals.

If you’re starting a new site today, there’s very little reason to reach for a page builder. If you’re running one, there’s increasingly a reason to plan your escape.

The hard parts that got easier

• Reusable patterns. Build a “testimonial section” once, drop it into twelve pages, update it in one place.
• Global styles. Change your brand color in one place and watch every block update.
• Full-site editing. The header, footer, and templates are editable alongside your content — no more “ask the developer to change the phone number in the footer.”
• Custom blocks. Developers can build purpose-specific blocks (pricing tables, team grids, menu cards) that content editors use like any other block.
• Data Views. Browsing posts, pages, and media now feels like a modern app instead of a 2010-era CMS.

The hard parts still hard

The editor isn’t perfect. Theme.json is still a JSON file, and editing it feels like configuring a build tool. Migrating a classic site to a block theme is work. Some custom-field-heavy workflows still feel awkward inside the editor.

But these are bumps, not walls. And they’re smaller than the bumps of any alternative.

Worth another look

If you last tried the block editor in 2020 or 2021 and decided it wasn’t for you, that was a reasonable decision at the time. In 2026 it isn’t anymore. Take twenty minutes with a fresh install and a modern block theme. You might find it’s the editing experience you’ve been wanting WordPress to have for years.

It finally grew up. That’s worth celebrating, even quietly.

Photo by Ron Lach on Pexels.