The making of
Nine days. 241 commits. Two AI orchestrators, a block theme, fifty-five patterns, and twelve real businesses built to prove it. Here's the honest archaeology — the pivot, the rollback, the spike we scored against ourselves, and the testing that earned the result.
The short version
It started as another WordPress theme. By day three it had become something nobody had shipped: the compiler that turns a one-paragraph brief into a real, editable WordPress site.
Most "AI makes you a website" tools are a thin wrapper over one model call. AgentPress is the opposite: a planner that decides the sitemap, writers that produce brand-voice copy, an image engine that keeps a consistent illustrated style across a page, a palette compiler that guarantees legibility by construction, and a pattern library that renders it all as native, hand-editable WordPress blocks. The interesting part isn't any one of those — it's the nine days of choosing, testing, and rebuilding that made them work together.
The build log
Pulled straight from the commit history and the dated working notes. Nothing dramatised.
v1.0.0 to v2.0.0 in a single day. Three style variations, a contrast-safe palette, per-variation headers and footers. The discipline showed early: v2.0.0's headline was a "design-system overhaul," not "add more features."
We built a pattern library and a scaffolder, then hit a wall: WordPress's full-width layout kept fighting our hand-authored markup. The note in the task list reads, word for word: "STOP and assess."
So we did. We read Automattic's own block-theming guidance, archived two versions of working-ish code, and rolled back to rebuild the whole pattern library on their verified foundation. Throwing away progress on day two to stand on firmer ground is the opposite of vibe-coding.
We stopped and asked a bigger question. The answer: the market doesn't need another opinionated theme — it needs the WordPress destination for the emerging DESIGN.md ecosystem. We rewrote the plan around a compiler, and committed to a rule we still hold: invent no new vocabulary. Material Design's token names pass through unchanged, end to end.
The busiest day — 52 commits. We spiked an alternative "match a rendered design to patterns" pipeline and set the bar before running it: clear 80% agreement with a hand-graded standard, or don't build the full corpus. It hit 83%. And when an early draft of the results overclaimed, the correction was written into the permanent record rather than quietly edited away.
Retry-and-fail-loud builds, multi-level site structure, a contrast validator that guarantees readable text by construction, and grounded content — sub-pages, suburb pages and blog posts written from real search data, never invented facts.
Stood up a dedicated iteration box and a dozen WordPress installs so we could rebuild whole sites in minutes and watch what actually changed — capturing each gotcha as a rule so it never cost us twice.
Consistent illustrated process sets instead of unrelated stock, the client's real logo composited onto a uniform in a signature shot, editorial-rhythm sections, sticky calls to action — then a browse-every-page audit of all twelve demos, fixing root causes, not symptoms.
Proof it was deliberate
Every one of these was tried, measured, and set aside for a reason. That's where the judgement lives.
The obvious first product. Set aside on day three — the market needs a compiler, not one more theme.
Full control, but it fought WordPress. Replaced with Automattic's verified pattern shape so it never drifts.
Could ingest any rendered design. Spiked to 83%, kept as a validated option — the simpler blueprint-driven path won.
Tempting branding. Deliberately rejected — Material Design's vocabulary stays intact end to end.
A fake "0400 000 000" on a real business is worse than none. Empty-unless-real is enforced at the source.
Replaced with scripts: contrast computed at the source, duplicate-image guarantees, live end-to-end checks.
What we stood on
The craft was in the integration, not in novel primitives. AgentPress consumes published standards and plugs into the ecosystem around it.
How we knew it was good
Quality was measured, not assumed.
A one-paragraph brief becomes a complete, editable WordPress site. The nine days are why it doesn't look like everyone else's.