WordPress is in the middle of a shift toward full-site editing (FSE), and the pace of change has left the tooling, documentation, and community knowledge badly out of step with one another. Theme and plugin development practices keep moving, yet the docs are often absent or close to stale by the time they are published. Even the name "full-site editing" may not survive; contributors have floated renaming it.
Tom McFarlin described the same gap from the tutorial side in his post "Writing Tutorials in These Gutenberg Times":
I know Gutenberg has been in development for five years and I know that it's matured a lot over the course of that time. But [t]he number of tutorials explaining how to do something that's already outdated was absolutely incredible.
Four Ways to Build a Site
Asked to stand up a new WordPress site today, a developer faces several legitimate but divergent starting points:
- A near-empty theme built on the Site Editor for templating and block patterns for layouts.
- A child theme of Twenty Twenty-Two, which supports FSE out of the box and is minimal enough to customize without much fuss.
- A classic theme.
- A headless front end consuming the WordPress REST API, with no theme at all.
Extending WordPress as a CMS now spans so many tools that the front end of one WordPress site can look nothing like another's. A complete custom site can be assembled purely by adjusting the theme.json file and arranging layouts in the Block Editor. That combination is impressive and disorienting at the same time.
Tension in the Open
Frustration with the transition surfaced publicly when Matt Mullenweg commented on the redesigned WordPress.org home and download pages and how long the work took:
[…] it's such a basic layout, it's hard to imagine it taking a single person more than a day on Squarespace, Wix, Webflow, or one of the WP page builders.
Someone subsequently recreated a nearly identical version of the design in 20 minutes using the Block Editor. Mullenweg's remark reads more as a question about process and about solving the right problems than as criticism of the approach taken. Still, the comment thread is a useful sample of the broader unease many WordPress developers feel after five years lived between classic and FSE themes.
Behind the Curve
FEELING out of step with FSE development is common enough to be worth naming: the worry is not just unfamiliarity but whether catching up is still possible. Learning resources are expanding — Learn WordPress is a strong example — yet something still feels absent. The disconnect persists between where the project actually stands and where the community believes it stands, and where it is heading.
Communication is not the weak point; there is plenty of it, along with ample meetings and meeting notes to attend or read. A lack of stable documentation is a real problem, especially when hunting for block development information.
The larger shortcoming may be the shortage of blog posts sharing tips, tricks, and best practices. WordPress has long had a generous community willing to pass on what it knows. But as McFarlin put it:
my sympathy to anyone who duckduckgo's/googles a tutorial for how to create a gutenberg block and cannot find a single consistent tutorial.
what a mess.
The desire to write about WordPress as prolifically as in the classic era is there. What blocks it is the same missing starting point — and the resulting doubt about whether anything written today will still be accurate tomorrow.



