After WordPress 6.1 arrived, I found myself thinking less about individual editor features and more about confidence. Block themes have been talked about for a while, and WordPress 5.9 made full site editing much more visible earlier this year. The question now is not whether the direction is real. The question is when I would trust it on the kind of client work where the site has to be maintained for years.
That kind of confidence does not come from a release post. It comes from building small sections, testing editor behaviour, handing the site to someone else and seeing where the friction appears. WordPress can introduce the tools, but the day-to-day experience decides whether those tools belong in a project.
What I Wanted To Test
The first area I wanted to test was whether block themes made normal editorial work clearer or more complicated. It is easy to get excited about editing templates visually, but most clients are not spending their day redesigning templates. They are adding pages, changing copy, replacing images and updating content that needs to remain consistent with the rest of the site.
That means the theme still needs to guide them. If the editor exposes too many layout decisions, the site can become inconsistent quickly. If it exposes too few, the new system does not feel much more useful than the old one. The balance is where the real work sits.
Patterns Are Still Doing A Lot Of The Heavy Lifting
The more I test block themes, the more important patterns feel. They give editors something useful to start from. Instead of assembling a section block by block, an editor can insert a designed structure and adjust the content. That feels much closer to how I want content-managed websites to work.
A good pattern is not just a layout convenience. It carries decisions about spacing, order, hierarchy and content relationships. Those are design decisions, and they should not be recreated from scratch every time someone adds a new section. Patterns allow the theme to keep those decisions visible in the editor.
This is also where block themes can start to feel safer. The editor can be flexible without becoming directionless. The client gets a set of approved building blocks, and the theme still protects the overall shape of the website.
Why I Would Still Be Selective
I would still be selective about where I use a block theme in 2022. Some projects need a highly controlled editing experience, especially where the site has complex templates, unusual content models or strict design requirements. In those cases, a classic theme with selected Gutenberg support may still be the better decision.
For content-led websites, though, block themes are becoming harder to dismiss. If the content structure is relatively straightforward and the client needs more control over sections, the block theme approach can make sense. The key is to plan the editor experience, not just the front end.
Retrospective Thoughts
WordPress 6.1 feels like another step in a longer transition rather than a single moment where everything changes. That is probably healthy. Most serious WordPress changes become useful gradually, as developers work out where they belong and where they do not.
My view is that block theme confidence will come from practical implementation. Build a small site. Test the patterns. Watch how the editor behaves. See what breaks when real content is added. That kind of learning is more valuable than deciding too early that every future WordPress site should use the same architecture.