Documentation · 3 min read
Editing your site
The site is not finished when the build stops. How a turn works, when to plan instead of build, and how to go back.
What a turn is
A turn is one message from you and everything that happens because of it. You describe a change in a sentence, the site is rebuilt to match, and the result appears in front of you.
It is the same motion as the first build. There is no separate editing mode to learn, no panel of settings, and nothing you have to find — describing the site and describing a change to it are the same act, and the second is usually shorter.
- "Move the contact form above the gallery"
- "The headline is too long — say it in six words"
- "Make the phone number the first thing on a mobile"
- "Add a page for the work you do in Leeds"
Tip. Ask for one thing at a time when you are being fussy about layout. Three at once works, and it is harder to tell which of the three produced the bit you did not like.
Build or Plan
Two modes sit beside the box, and the difference is whether the turn is allowed to ask you anything before it starts.
Build
Takes what you said and makes it. The right default for a change you can describe completely — moving something, rewording something, adding a page you have already decided on.
Plan
Lets the turn ask questions and sketch what it intends before building it. Worth it when the request is bigger than a sentence: a whole new section, a shop, a rework of how the site is organised.
The questions are the point. A build that guesses at what you meant costs the same as one that asked first, and then costs again when you correct it.
Note. The choice is remembered between visits, so whichever you pick becomes your default until you change it.
Going back
Every turn is kept. The version list holds what the site looked like before each change, so a turn that went somewhere you did not want is one press to undo rather than a conversation to unpick.
This is worth knowing BEFORE you need it, because it changes how freely you can experiment. The cost of trying something odd is one turn, not the site.
- Open the version list in the editor.
- Find the state you want — they are listed newest first.
- Restore it. The site returns to exactly that.
What a change costs
A turn is charged for what it actually uses rather than at a flat rate. That is the whole reason nudging a heading and building a site from nothing do not cost the same.
In practice: a first full build is the expensive one, and the small corrections afterwards are a fraction of it. There is a small minimum on every turn, so a one-word change is not free — but it is close to it.
Roughly what to expect
- A first full build
- The most expensive turn you will run
- Adding a page
- Well under a first build
- Rewording or moving something
- Near the minimum
- A turn that failed
- Nothing — see below
Note. The real figure for each turn is shown against the reply it produced, so you never have to estimate. Nothing here is a quote — the cost sits on the turn itself.
Common questions
Can I edit the code directly?
The files are visible in the editor, and the export gives you all of them. Describing the change is the supported route and the one everything else is built around.
What if a turn goes wrong?
Restore the previous version from the version list. The turn that went wrong stays in the transcript, which is often the more useful record — it says what was asked for and what came back.
How specific should I be?
More specific than feels necessary. "Make it look more professional" is a sentence with a hundred readings; "tighten the spacing and use one accent colour instead of three" is one.
Does changing the site break the dashboard?
No. Leads, visitor counts and products belong to the site rather than to any version of it, and rebuilding the pages does not touch them.
