Update a page with your AI

A live page isn’t finished; it’s just live. With your assistant connected, you change it the same way you made it: by asking.

Just describe the change

“Add the opening hours under the photo.” “Make the header green, like the logo.” “Add a section with prices: three tiers.” “Fix the typo in the title.”

The assistant updates the page and re-publishes. Your address never changes; visitors simply see the new version.

Every change is a version

Each publish is kept as a version with a short label of what changed (“Add contact form”). Nothing is ever overwritten: if a change turns out worse, restore any earlier version in one click, from the dashboard, or by asking (“go back to yesterday’s version” also works, the assistant can see the list). Details: Versions & rollback.

Ask for your numbers, too

The same conversation reads your results:

“How many people signed up this week?” “What did the contact form receive?” “Which of my links gets the most clicks?”

The assistant only ever reads your sites’ data: the same figures as your dashboard’s Data and Analytics tabs.

Coming back later (or in a new chat)

You don’t need to keep one eternal conversation. In a fresh chat, just name the site: “update my atelier-terre page”. The assistant re-reads the project from Bailey: what it’s for, what it collects and under what rules, its current state. Your intent lives with the project, not in an old chat log.

The rules that protect you while you iterate

Data collection can’t quietly grow. If a change starts collecting something personal that wasn’t declared, the purpose-and-retention questions come back before anything publishes. No silent scope creep.
Existing data is protected. A field that already holds submissions can’t be renamed or dropped on a whim; Bailey refuses changes that would orphan real records.
You can always pull the plug. “Take it offline” unpublishes the site on the spot; “bring it back” restores it.