WordPress 6 and the Gutenberg question.
WordPress hit version 6 last week, and the block-editor era is now firmly the default. We still ship WordPress sites. We are also more careful about when to.
WordPress 6 shipped in May. The block editor — Gutenberg — has been the default since 5.0, but the rough edges are mostly gone now. We still ship WordPress sites every year, and we still hold opinions about when it's the right tool.
When WordPress still wins
- 01Content-managed marketing sites where a non-technical team owns the day-to-day.
- 02Anywhere the client already has a WordPress operation and a writer who knows it.
- 03Blogs and editorial sites — WordPress is genuinely the most usable CMS in this category.
- 04Anything with a third-party plugin ecosystem requirement (membership, paid courses, BuddyPress).
When we steer away
- 01Heavily interactive product surfaces. WordPress wasn't designed for that and the patches show.
- 02Anything where SEO of a fast-loading SPA is the primary need — modern Nuxt or Astro is a better fit.
- 03Headless setups where the content team is small and disciplined — they'll outgrow the WordPress admin within a year.
The decision matrix we apply
| Brief shape | CMS we reach for | Why |
|---|---|---|
| Editorial site, daily content team | WordPress | The admin is what editors already know |
| Marketing site, occasional updates | Nuxt Content | Smaller, faster, easier to host |
| Headless product with a real CMS need | Sanity / Strapi / Payload | Content modelled like data, not pages |
| One-off marketing landing page | Static HTML or Astro | No CMS overhead at all |
| Membership / course platform | WordPress + LearnDash / MemberPress | The plugin ecosystem genuinely earns its keep here |
Gutenberg, honestly
The block editor in 2022 is fine. It's still not as composable as a real headless model, and bespoke block development is heavier than the equivalent component work in a modern framework. But for a marketing team who needs to publish a Tuesday blog post about a Wednesday event, it works and it scales.
If the content team is the primary user, WordPress is on the shortlist. If the engineer is the primary user, it isn't.
Our rule of thumb: if the content team is the primary user, WordPress is on the shortlist. If the engineer is the primary user, it isn't.