> ## Documentation Index
> Fetch the complete documentation index at: https://docs.boostgpt.co/llms.txt
> Use this file to discover all available pages before exploring further.
# Site Builder
> Edit your Site visually, and control exactly what goes live
## The one thing to understand first
Your Site has **two copies**: the one you are working on, and the one your visitors see.
| | What it is | Who sees it |
| --------------------- | ------------------------------------------------ | --------------------------- |
| **Working copy** | What the agent writes and what you edit visually | You, in the builder preview |
| **Published version** | A frozen snapshot you chose to publish | Everyone on your public URL |
Editing never changes your live Site. Neither does asking the agent to rebuild a section. Your public URL keeps serving the exact bytes of the version you published until you publish again.
This means you can rebuild a page in the middle of the day with real visitors on the site, and they will keep seeing the last version you published.
## Builder views
The toolbar above the preview holds a view switch and two toggles.
| Control | What it does |
| ------------------- | ---------------------------------------------------------------------------------------- |
| **Preview** | Your Site as visitors would see it, using the working copy |
| **Files** | The underlying files, for working with them directly |
| Settings (gear) | Publishing, custom domain, the support agent, and everything your Site's forms collected |
| **Edit** | Turns on visual editing — click any element to select it |
| Canvas (frame icon) | Lays every page out side by side on a board |
**Edit** and **Canvas** are independent toggles, so you can use them together — restyle elements while looking at your pages at once.
When a Site has more than one page, a page switcher sits in the toolbar. Choosing a page previews it, and following a link inside the preview moves the switcher with you, so you always know which page you are looking at.
## Editing visually
Turn on **Edit**, then hover to outline an element and click to select it. A toolbar appears below your selection.
| Control | What it changes |
| ---------------- | ------------------------------------------------------------------- |
| **Edit Element** | Sends the element to the chat so you can describe a change in words |
| **Regenerate** | Asks the agent to redesign that element, keeping its content |
| **Edit text** | Edits the text in place — appears for text elements only |
| **Font** | Family, weight, and your own uploaded fonts — see below |
| **Size** | A preset scale, or type your own value |
| **Alignment** | Left, centre, right, justify |
| **Colour** | A swatch grid, or a hex value |
| **Classes** | The element's raw CSS classes |
| **Source** | Read-only view of the element's opening tag |
| **Undo** | Reverses your last edit |
| **Delete** | Removes the element |
Edits save as you make them. Font, size, alignment and colour are written as inline styles on that one element, so they work whether your Site uses utility classes or its own stylesheet. Picking a font also adds its webfont to the page, so the choice actually renders instead of quietly falling back.
Every visual edit is recorded in version history, so nothing you change here is unrecoverable.
### Choosing a font
Search by name, or narrow the list with the category filter — **Sans serif**, **Serif**, **Monospace** or **Display**. Each name is shown in its own typeface, and the arrow beside it opens the weights: Light, Regular, Medium, SemiBold and Bold.
Picking a Google font adds its webfont to the page automatically, so the choice renders rather than falling back to a default.
To use your own typeface, choose **Upload font** and pick a `.woff2`, `.woff`, `.ttf` or `.otf` file up to 2MB. The file is stored with your Site's other files, so it is versioned and published along with everything else — no external hosting to keep alive. Uploaded fonts appear under **Site fonts** at the top of the list.
Fonts already on the page — uploaded, or wired up by the agent — are listed under **Site fonts**. Removing one is a job for the agent; the picker only adds.
### Undoing an edit
**Undo** in the toolbar reverses your last change, and keeps going back through the edits you made in this session. It covers styling, classes and text.
Two things it does not cover, both of which version history handles instead:
* **Deleting an element** — restoring it needs the original markup, so roll back to an earlier version
* **Edits from before the agent last changed the page** — when the agent rewrites a page, earlier undo steps no longer point at the right elements and are discarded
### Editing text
Double-click a text element to edit it in place, or use **Edit text** in the toolbar.
| Key | Result |
| ----------------- | ----------------------------------- |
| **Enter** | Keeps the change |
| **Shift + Enter** | Adds a line break and keeps editing |
| **Escape** | Discards the change |
| Clicking away | Keeps the change |
Formatting inside the text — line breaks, bold or italic runs, accent spans — is preserved.
### When the agent edits at the same time
If the agent rewrites the page while you have it open, the builder reloads to show you the agent's version rather than overwriting it. You will see a short notice when this happens. Reapply your change on the fresh copy.
## Canvas
**Canvas** lays your pages out side by side on a board, so you can judge the whole Site at once
rather than one page at a time. Each page is a live frame — what you see is the working copy, not
a screenshot.
| Action | How |
| ------------------- | ------------------------------------------------- |
| Zoom | The − / + controls, or `Ctrl`/`⌘` + scroll |
| Pan | Scroll, or drag the background with the hand tool |
| Fit everything | `⌘1` |
| Back to actual size | `⌘0` |
### Moving around the board
The toolbar has a **select** tool and a **pan** tool. With select, click a frame to pick it up and
drag it anywhere on the board, or drag its edges to resize. Each page frame also has a device
selector, so you can sit a phone-width frame next to a desktop one and compare.
Clicking empty space deselects everything.
### Annotating
Canvas is also somewhere to think. Alongside the pages you can add:
* **Notes** — double-click to edit; useful for "this headline is too long"
* **Drawings** — freehand marks with the draw tool
* **Images** — drop a reference or a screenshot onto the board
* **Connectors** — drag from the dot on any element's side to another element to link them
Annotations live on the board, not in your Site. They are never published and never appear to
visitors. **Undo** and **redo** cover everything you do here, including deletions.
Annotations belong to the Site, not to you, so anyone who can open the builder sees the same
board.
## Version history
Open version history from the clock icon in the preview toolbar. It takes over the chat panel, so your preview stays where it is.
### What creates a version
* **Each agent turn** — one version per completed build turn, titled from what the agent did
* **Your own edits** — grouped into a single **Manual Edits** version rather than one per click. The group stays open while you keep working and closes when any of these happen:
* about five minutes pass without an edit
* the agent makes a change of its own
* you publish
* you roll back to another version
### Reading the list
| Badge | Meaning |
| --------------- | ------------------------------------------------- |
| **Live** | The version your public URL is currently serving |
| **In progress** | An open group of manual edits that may still grow |
| **Current** | The newest version — what the preview shows |
### What you can do with a version
Opens that version read-only in the builder so you can see it before committing. Choose **Stop previewing** to return to your working copy. Preview links are private to you and are never indexed by search engines.
Points your public URL at that exact version. Use it to go live with an older version without disturbing what you are currently working on.
Copies that version's files back into your working copy, as a **new** version on top of the history.
Rollback moves forward, never backward. Restoring an older version adds a new entry rather than deleting anything, so the versions you rolled back past are still there and can be restored again.
## Publishing
Publishing takes your **current working copy**, freezes it as a version, and points your public URL at it.
Open **Settings** in the builder toolbar, then **Publishing**.
Check the working copy in the builder. This is what will go live.
Your Site's public URL now serves that snapshot.
Further edits go to the working copy. The live Site does not change again until you publish.
Your Site's thumbnail refreshes after a version goes live, so the card in your dashboard reflects what visitors actually see rather than a half-finished build.
### Using your own domain
Once a Site is published, **Publishing** also holds its custom domain. Add a domain you own, then
create the CNAME record shown against it at your DNS provider. The status stays **Pending** until
the record resolves, then becomes **Active** with SSL provisioned.
DNS changes take time to propagate — use **Refresh** to re-check rather than expecting it to
flip immediately.
## Forms
If your Site has a form, its results show up in **Settings** with an export: people who joined a
list appear under **Leads**, and every other form’s answers under **Collections**. See
[Forms](/creators/forms) for how to ask the agent for a form and what you can collect.
## Putting your agent on the Site
**Settings → Agent** adds your agent to every page as a chat bubble, so visitors can ask questions
about what you are building. It answers from the same training as your public agent.
It is **off** until you turn it on, and takes effect immediately — no republishing. It appears on
the published Site and on your preview so you can try it first, and never while you are editing
visually or viewing an older version.
Do not ask the agent to build a chat widget into the page. Turn this on instead — it is injected
when the page is served, so it stays out of your files and out of version history.
## Attachments
Files you attach in the builder and files visitors attach in public conversations are separate
permissions.
### Creator attachments
Creator attachments are available from **Free**. They always use your plan's file-count and size
limits, plus BoostGPT's platform-safe file validation. They do not depend on the public Agent's
visitor attachment toggle or accepted-type preset.
### Visitor attachments
Open **Agent settings → Visitor attachments** to decide whether people using your public Site chat
may attach files. Visitor attachments require both a plan that includes them and the Agent toggle.
The Agent's maximum size, files per message, and accepted file types are then enforced again when
the visitor submits the message.
New and existing Hobby/Pioneer Agents start with visitor attachments off. Turn them on explicitly
for each Agent. Starter and higher Agents keep the existing enabled-by-default behaviour. Free
Agents cannot accept visitor attachments, even if an older stored setting says otherwise.
| Plan | Creator attachments | Visitor attachments | Per message |
| --------------- | ------------------- | --------------------------- | -------------------- |
| Free | Yes | No | 1 file, 2 MB |
| Pioneer / Hobby | Yes | When the Agent toggle is on | 3 files, 5 MB each |
| Starter | Yes | When the Agent toggle is on | 5 files, 5 MB each |
| Pro / Prime | Yes | When the Agent toggle is on | 10 files, 10 MB each |
| Scale | Yes | When the Agent toggle is on | 20 files, 25 MB each |
Each accepted attachment costs two ordinary message credits.
## Reviews & autonomy
Every Site has one review schedule. Open **Settings → Reviews & autonomy** to choose how often the
Agent checks the Site and how far it may take work without you. Free includes monthly reviews;
Hobby/Pioneer add weekly, Starter adds daily, and Pro/Prime/Scale add a rolling hourly review.
Cadences your plan does not include remain visible and show the tier that unlocks them.
The review files recommendations to Backlog and changes nothing by itself. The autonomy rung
controls what can happen after that; publishing remains a separate decision.
Forms work on the preview as well as the published Site, so you can test one before publishing.
Preview submissions are stored like real ones, so use an address you can recognise later.
## Limits
Sites built as an app shell generate their markup in the browser at runtime, so there is nothing in the stored file to point at. The builder tells you when this is the case. Ask the agent to make changes instead — everything else, including version history and publishing, works normally.
If your page uses JavaScript to build content after it loads, those elements do not exist in the source file and cannot be selected. Clicking one selects the nearest real element that contains it. Ask the agent to change the code that generates them.
Publishing pins every page at that moment. You cannot publish one page while holding another back, so finish the set before going live.
## Good habits
* Publish at a point you are happy with, then keep experimenting — the live Site is safe while you do
* Use the agent for structure and layout, and the visual editor for wording, colour and type
* Before a big change, note which version is **Live** so you know where to roll back to
* Preview a version before publishing it, especially when going back to an older one