I love WordPress, and I love being able to turn an idea into something I can try with prompts and revisions.
So when I read WordPress.com’s recent post “AI Website Building: Separating Hype from Reality,” I found myself nodding at parts and frustrated by others.
The post sets up a choice that doesn’t need to exist. It puts vibe coding tools in one box (fun for experiments, dangerous for real work) and WordPress in another (the grown-up choice for serious people). But why? These aren’t competing philosophies. They’re complementary tools in the same toolbox.
I’ve built WordPress blocks with Cursor and brought AI prototypes into WordPress. I use whichever tool helps with the next step.
The article raises fair concerns about complexity, security and breakage. I think we should teach people to handle those risks, just as we do with WordPress, rather than discourage them from trying the tools.
What bothers me most is the underlying message: you’re not ready for this. People said similar things about WordPress when it launched. New tools often let more people do something that used to need specialist help.
Someone can try an idea without hiring a developer first. Some projects will use WordPress. Others will start as prototypes and move to a platform that suits them as they grow.
That seems like a useful way to work.
There’s room for both.
END OF TRANSMISSION · FILE SAVED
Transmission complete.
The workshop keeps humming. Teddy stamps the paper and pretends this was all according to plan.
ONE-TAP PRIVATE SIGNAL
What kind of noise did this make?
One click sends Nick a tiny private light on the console. No account, count, leaderboard, or public performance.

INCOMING TRANSMISSION
What did this signal make you want to build, remove, or argue with?
Send Teddy a note about Use WordPress and vibe coding together. It goes straight to Nick’s normal email inbox. No admin screen and no public comment thread.
KEEP THE RECEIVER ON · RSS ↗