Full Site Editing in 2026: Is Gutenberg Finally Ready?

Full Site Editing has been “the future of WordPress” for long enough that the phrase itself has started to feel dated. It’s worth actually checking where FSE stands against WordPress’s own official roadmap, rather than either the breathless “Gutenberg finally works” takes or the tired “it’s still not ready” dismissals — both of which tend to be more opinion than status update.

The roadmap, as WordPress itself has defined it

WordPress’s official roadmap describes Gutenberg’s development in four phases. Phase 1, Easier Editing, is the original block editor itself — shipped, long stable. Phase 2, Customization, covers full site editing — themes built entirely from blocks, editable through the same interface as post content — and that phase culminated around WordPress 6.3. Phase 3, Collaboration, is the current active phase of work, and it got its first genuinely shipped feature with block-level Notes in WordPress 6.9 (December 2025) — real-time, in-editor commenting on specific blocks. Phase 4, Multilingual, covering native multi-language support in core, has not started as official development work.

That framing matters because it clarifies something people often get backwards: full site editing itself isn’t the unfinished part. Structurally, Phase 2 already culminated with WordPress 6.3. What’s still actively in progress is Phase 3 — collaboration features — which is a genuinely different, later-stage set of work than the core FSE capability itself.

FSE the capability and FSE the ongoing roadmap are two different things. The capability has been structurally complete since roughly WordPress 6.3. What’s still unfinished is the collaboration layer being built on top of it.

What’s actually shipped as tangible proof

Twenty Twenty-Five, bundled as WordPress’s default theme starting with 6.7 (November 2024), is a full block theme — meaning the flagship, out-of-the-box WordPress experience for new sites is now built on FSE by default, not on classic PHP templates. That’s a meaningful, concrete signal about where WordPress core itself has placed its bet, independent of how much of the broader ecosystem has followed.

Where I’d be honest about the limits of what’s verifiable

I want to be direct about something: a lot of the commentary you’ll find on “FSE adoption rates” — specific percentages of sites using block themes, or claims about how much block-theme usage has grown year over year — traces back to unofficial blog posts and commentary, not verified data from WordPress.org itself. I couldn’t confirm any specific adoption percentage against an official source while researching this, and I’d treat any number you see quoted with real skepticism unless it’s directly sourced. What’s verifiable is the roadmap status and what’s shipped in core — not a reliable, sourced measure of how much of the broader WordPress ecosystem has actually adopted it.

Is it actually “ready,” practically speaking

Setting aside adoption statistics I can’t verify, here’s my honest, hands-on assessment of where things stand:

• For a straightforward content site — blog, small business site, portfolio — a modern block theme built on FSE is a genuinely solid choice today. The editing experience is mature, the Style Book and global styles system (refined further in 6.8) makes design consistency easier to manage than it used to be, and Zoom Out mode (from 6.7) makes structural editing more intuitive.
• For a complex, highly custom site with specific functional requirements — heavy WooCommerce customization, complex membership logic, tightly bespoke layouts — classic themes and page builders still often provide more direct control, and a lot of that ecosystem hasn’t fully caught up to block-theme patterns yet.
• The collaboration features (Phase 3) are genuinely new, having only just started shipping with 6.9’s Notes feature — if multi-person editorial workflows are important to you, this is worth testing directly rather than assuming it matches the maturity of the core editing experience, which has had years longer to develop.

What tends to actually decide the outcome on a real project

In practice, the classic-versus-block-theme decision on a specific project usually comes down less to “is FSE technically ready” and more to what your existing team and existing plugin stack already know how to work with. A team fluent in classic PHP templating switching to a block theme mid-project takes on real, if temporary, friction that has nothing to do with whether FSE itself is mature — and a plugin ecosystem built around classic-theme hooks and filters doesn’t always translate cleanly to block-theme patterns yet, even for otherwise well-maintained plugins. That practical, team-and-stack-specific friction is often the deciding factor in real projects, more than the abstract question of the technology’s overall readiness.

The honest verdict

“Is Gutenberg finally ready?” is really two separate questions wearing one costume. Is the core full-site-editing capability structurally mature? Yes — it has been for a while now, and WordPress’s own choice to make Twenty Twenty-Five a block theme is a concrete vote of confidence in that maturity. Is the broader roadmap — specifically the collaboration and multilingual phases — finished? No, and Phase 4 hasn’t even started. Whether FSE is “ready” for your specific site depends far more on what you’re building than on where WordPress is in its own multi-year roadmap.

If you’re deciding right now, for a new project

For anyone actually facing this decision today rather than evaluating it in the abstract, the practical test I’d apply is simple: build a small, real piece of the site — a homepage template, one archive layout — in a block theme before committing to it for the whole project. That hands-on test surfaces whether your specific plugin stack and design requirements play well with FSE far faster than reading roadmap status ever will, and it costs a fraction of the time a full rebuild-and-migrate-back would cost if you commit first and discover friction later.