WordPress Development
In development. Taking enquiries.
- ·Themes, blocks and the content model, kept simple enough that the people who own the site can edit it without breaking it.
- ·Offered because clients ask for it by name, and said plainly: the openable sample does not exist yet.
| Becomes live when | A sample site a stranger can open in a browser sandbox is published alongside its theme source. The procedures that deliver this work exist and are named above; the sample is the only missing part. |
| Built with | WordPress · Puppeteer |
| Delivered by | · refactor-specialist |
| Skills used | web-qualify · wp-build · web-handoff |
What this involves
Most WordPress work that goes wrong goes wrong the same way: a plugin is added to solve a problem, a second plugin is added to solve what the first one broke, and two years later nobody can update anything. The work here is the opposite of that. Read the theme, read the database, remove what is not carrying weight, and keep the content model simple enough that the people who own the site can edit it without breaking it.
Adjacent experience is real and is on the career record: an ongoing programme of legacy WordPress migrations at an employer, with AI-assisted content extraction rather than manual copy and paste. That work sits on client sites which are not public, so it is a job rather than a sample, and this page does not present it as one.
The honest state of this service is that it is offered because clients ask for it by name, and that there is nothing here a stranger can open. The condition for changing that is above: a sample site in a browser sandbox, with its theme source alongside it.
How the work runs
1. Discovery
We agree what the project has to achieve, what it must not break, and how we will both know it worked, before any code is written.
2. Build
The work is built with an AI agent as the working partner and a human reviewing every change before it lands. You get commits you can read rather than a status update.
3. Review
You review running software at each milestone, not a screenshot of it, and the next milestone absorbs what you send back.
4. Launch
We deploy to production with checks in the pipeline and alerting that reaches a human, and you hold the repository and the infrastructure accounts.
Questions people actually ask
Is WordPress still a reasonable choice?
For a content site with non-technical editors, often yes, and the alternative is frequently worse for the people who have to update it. It stops being reasonable when the site is really an application wearing a content management system, at which point every new requirement is fought against the platform rather than with it.
Can an existing site be repaired rather than rebuilt?
Usually, and it is normally the cheaper answer. The first work is reading: which plugins are load-bearing, what the theme has been modified to do, and what the database looks like underneath. A quote that skips that phase is a quote that gets revised.
What is missing from this service right now?
A sample, and a specialist. There is no WordPress build here a stranger can open, and the migration specialist this work wants has not been built in the ecosystem that delivers it, so it currently runs on general engineering members. Both are stated on the page rather than left for a client to discover.