01The bet each side made
New here? Start at the pillar page for the full picture.
WordPress bet that editing a website was too hard for normal people, and it was right for twenty years. The visual editor, the database, the plugin ecosystem: all of it exists to put a browser between a person and the code. The price of that bet is the maintenance list, paid monthly in money or in evenings.
A coding agent bets you can describe a change and review the result. "Update the prices and fix the form, then push." The edit happens in real files, you read the diff, and the push deploys. No browser editor sits in between, so no PHP application sits underneath.
02The two bets, side by side
The browser editor bet
Non-technical people edit visually, safely, with roles. Costs: the update cycle, the plugin surface, an admin login, forever.
Wins outright when staff editing and plugin workflows are hard requirements.
The agent bet
You describe changes in language, review a diff, push. Costs: someone must be able to review the result.
Wins the common case: a site that changes occasionally and must never be the 2am emergency.
03Where WordPress keeps the crown
WordPress keeps the crown where many people must edit with roles and approvals, where a shop or memberships run on its plugins, and where a workflow genuinely depends on one. Those are real sites and real reasons.
The agent workflow wins the common case: a site that changes occasionally, owned by someone who never wanted to be a webmaster, who would rather type the change than learn a dashboard. It also removes the small-change tax, where every edit was either a favour from someone technical or an invoice. And the safety story is not worse: a bad push rolls back faster than a broken WordPress update recovers.
04The question to ask yourself
Who edited the site in the last three months, and how did it feel? If the answer is "me, in the WordPress admin, and it was fine", you have a working system and this page changes nothing. If the answer is "nobody, because it has become a chore", the editor was solving a problem you do not have, and the static alternative plus an agent is the smaller machine.
05Frequently Asked Questions
Do I need to understand code?
You need to describe changes in plain language and read the result. The agent handles the code the way WordPress handles the database: out of sight.
Can an agent wreck my live site?
It pushes like any developer, so a bad change goes live until you roll it back, which takes seconds from the deployment history. Reviewing a diff before pushing stays a good habit.
Which agents work?
Anything that can use GitHub: Codex, Claude Code, Cursor, Hermes. Publishing is agent-neutral because the repository is the interface.
Can I start from my existing WordPress site?
Yes. The migration guide covers the export, and the agent rebuilds the design so you are not starting from a blank page.
Build it with your AI. Host it here.
Deploys on every push, from Australia, with nothing to maintain.