Your website is written for you, not filled into a template

The biggest change under the hood since we launched: building a website is now an act of writing it rather than filling your details into a layout we already had.

A stronger model does the authoring

Generation moved to Sonnet 5. The difference shows up in the least glamorous place — your own words. Given the same brief, the previous model paraphrased the headlines you wrote and drifted back towards house defaults, so two businesses in the same trade came out reading like each other. The site you get now keeps what makes the brief specific: your phrasing, your offer, the details you bothered to mention.

Edits still run on the fast model, so changing a headline stays quick and cheap. It's the initial build that got the expensive treatment, because that's the one you judge us on.

Booking and contact pages that belong to your site

Until now, /booking was a hardcoded page. Identical markup, identical grey fields, identical spacing — on every website we have ever generated, regardless of what the rest of the site looked like. Clicking "Book" was a visible step out of your brand and into ours.

That page is now designed along with the rest of your site: your colours, your type, your layout, your wording. Contact forms got the same treatment.

What did not move is the wiring. The part that talks to the appointment system — endpoints, time zones, which slots are free, the deposit hand-off to Stripe — is hand-written, shipped as-is, and off limits to the model. Design is generated; plumbing is not. Before a site ships we check that a page offering booking is actually connected to the real booking system rather than to a form that looks convincing and goes nowhere.

Checked before it reaches you

Every build is now compared against the plan that was made for it before anything is published. Sections in the plan but missing from the page, a menu item pointing at a part of the page that doesn't exist, a component used but never imported — these are found automatically, and most are corrected without a model call at all.

Dead menu links were the single most common defect, and they came from something structural: the navigation and the page are written separately and can't see each other, so they disagreed about section names on most builds. That's now settled mechanically, in milliseconds, instead of costing two full page rewrites and pushing the build past its deadline.

Fixed: long builds that were cut off mid-way

Builds have a hard time limit set by our host. Authoring a site takes longer than filling in a template, and after the change above some builds simply ran past it — at which point they were killed, with no error that explained anything. Depending on where it happened you'd get a much simpler site than the one being written for you, or a build that just stopped.

Three fixes:

• The ceiling went from 300 seconds to 800, which is the platform maximum. One build route had no ceiling set at all and was inheriting a much lower default — it's now aligned with the rest.
• The time set aside for publishing after generation was measured rather than guessed (it costs ~38s, we were reserving 90s) and the difference handed back to building your site.
• When the builder does run out of time it now ships the site it has built instead of discarding it. Running long costs you the last refinement, not the whole website.