WordPress isn’t the problem. The theme is.

“You can only build basic websites with WordPress.” You’ve heard it a thousand times. That every template looks the same, that it got stuck in 2010, that it never managed to ride either the AI wave or the modern-tooling one. It’s one of those prejudices that, repeated often enough, ends up sounding like the truth.

Here’s the spoiler: they’re almost never talking about WordPress. They’re talking about the theme.

The misunderstanding: WordPress isn’t its face

When someone builds a “regular” WordPress, they install a theme: that layer that mixes PHP with HTML, leans on dozens of hooks and drags along an aesthetic you can smell as a template from a mile away. The theme is the skin. And yes, plenty of skins are generic, slow and hard to bend to your will. That’s where the bad reputation comes from.

But under that skin sits one of the most powerful, battle-tested content managers on the planet: an editor millions of people already know how to use, roles and permissions, revisions, a media library, a huge ecosystem and an API that ships out of the box. None of that is “basic”. What was basic was the theme we bolted on top.

The problem was never the engine. It was the bodywork we screwed onto the front.

The idea: take its head off

“Headless” (or decoupled) means exactly that: we take WordPress’s head off. We keep what it does brilliantly —storing and serving content— and throw the presentation layer in the bin. We build the front end separately, with modern technology, and ask WordPress for the content through its API.

WordPress becomes the brain. The front end, the pretty face. And the beauty of it is that, looking at the pretty face, nobody —absolutely nobody— guesses there’s a WordPress behind it.

Why I got into this

I started this project with one specific obsession: to dismantle the story that “you can’t do it with WordPress”. I wanted to prove you can use it as a CMS and put a spectacular front end in front of it, one that makes you say “wow, what a site” the moment you land, without smelling of WordPress or of an AI template. Both of those had to go.

Because this isn’t about ditching WordPress to look modern. It’s about keeping its best part —a comfortable editor for whoever writes— and not paying the price of its worst part —a straitjacketed design layer. The best of both worlds, without either one’s toll.

This very page is the proof

It’s not theory. Every word you’re reading comes from a perfectly ordinary WordPress, served by its API. The design, on the other hand, is 100% bespoke: the typography, the rhythm, the colour, every micro-animation. And it flies —100 out of 100 on Lighthouse performance, zero JavaScript by default. The medium is the message: the site itself is the argument.

When does it make sense?

You want a fast, bespoke design, but you want someone to edit the content without touching code.
You already have a WordPress full of content and don’t want to migrate it, just give it a new face.
You genuinely care about performance and security (the WordPress isn’t even exposed to the public).

When maybe not? If it’s a tiny blog with no design ambition, a classic WordPress will do and saves you moving parts. Here we’re talking about when you want something that stands out.

Shall we build it?

The rest of this guide is the step-by-step, start to finish. And if you want your own AI agent to come along, copy it this single block: it installs the wp-wow skill and tells it what to do. That’s everything it needs.

Install the wp-wow skill and use it to build my project:

npx skills add HombreFeliz/wp-wow

Then follow it: build a headless WordPress with a premium Astro front end
following the wp-wow skill. Start by spinning up the CMS locally
and checking that /wp-json responds, and explain each step to me.

No agent? You can follow the guide by hand too. In the next chapter we start at the beginning: stripping WordPress to the bone so it does one thing, and does it perfectly.