Drafts, publish, and rollback

Once a site is in your workspace, edits land in a draft. The live site only changes when you publish.

Two URLs

How versions work

• Every deploy or source write creates a new version, with a commit message from the agent: a one-line summary you see in History, and underneath it, when you open the version, what changed and why. History is append-only; old versions stay. You can see, restore and roll back to versions from the last 30 days on Free, the last year on Hobby, and all of them on Pro; older ones come back if you upgrade. The live and latest versions are always available.
• To change a few words yourself, open Edit text in the Preview tab, click the text and type. Nothing is saved until you review the changes and press Save. History shows these as Editor, beside your name. This works on sites made of uploaded HTML files too: text written in the file can be changed; text the page's own scripts add, and files that are minified or generated by another tool, can't, and the editor says why. The style toolbar, Sections and Props below are for sites built from pages.
• To restyle something on a site that uses Tailwind, click it in the same editor and use the toolbar that appears above it: background, border and text colour (your site's colours, or any colour from the picker; backgrounds can also be a gradient), border and corners, layout (flex, alignment, gap), padding and margin for all sides or one side, font, text size, weight, alignment, line height and letter spacing, opacity, and width and height under ⋯. The menu at its start styles one screen size and wider (like tablets and up) or a state such as hover instead. The page shows each change straight away; it's saved the same way.
• In the same editor, Layers lists every element of the page in order: click one to select it, drag one to a new place (in the list or on the page), drop it on another element to move it inside that one, move it up or down (Shift+↑ and Shift+↓ also work on the selected element), remove it, or add one of your site's own components. A move shows on the page straight away. Props changes a component's settings, such as its title or style option, for the part you clicked. Insert adds text, a heading, a box, a button or link (it asks where it goes), an image or one of your components (shown as a placeholder until you save) inside the element you clicked, just after it, or at the end of the page; images come from your site's images, and you can upload one there. Click an image to replace it or change its alt text, which is what screen readers say. The bar at the bottom of the page does the same in place: pick Box (R) or Text (T) and drag on the page to draw it where it goes (a text is ready to type into straight away), or add an Image or one of your Components; Select (V) goes back to clicking. New elements show on the page straight away. These are saved with your other changes when you press Save.
• Publish points the live site at a ready version. If the quality gate fails, the live site does not change.
• Rollback re-publishes an earlier version instantly.
• Look before you restore. In History, open any version to see exactly what it changed and browse the site as it was. Agents use list_changes, diff_source_file and preview_version. Nothing changes until you restore.
• Unpublish takes the site offline without deleting history.

Several people or agents on one site

Several people and agents can edit one site at the same time, with nothing to lock. Every version records who wrote it and with which app (for example Claude Code), so the history shows who changed what. When two agents change different parts of the same file, both changes are kept. When they change the same lines, the second one is shown both versions and asked to combine them, so nobody's work is silently overwritten. On a static site, an agent changing a page has to say which version it read. If someone else saved a newer one in between, their changes and its own are combined the same way; only when both changed the same lines is it stopped, told who made the other change, and asked to re-read before trying again. Ask your agent to publish the exact version you previewed: someone else may already be halfway through newer edits. Publishing a version also puts live every change made between the last publish and that version, including other people's, so the agent is told whose changes went out with yours and passes that on. Anything newer stays a draft, and publishing an older version puts nothing new live.

Git history

Signed-in sites also keep a read-only git copy of their history: one commit per version, with the time and who wrote it. Agents ask for it with get_git_access and can then git clone, git log and git blame the site like any repository. Images and other media are listed by checksum rather than copied in. The copy follows your edits within a few seconds; edits still go through Webly, so the history in Webly and in git always match.

Password protection

On Hobby and Pro you can put a password on a site: open it in the dashboard, go to Settings, and choose Set password (or ask your agent). It covers every address the site has, the draft included. Visitors see a short password page; once they enter it, that browser stays unlocked for 7 days. Changing the password signs everyone out. Webly keeps only a scrambled copy, so it can't show you the password again: send it along with the link. Removing it works on any plan.

Quality gate

Framework sites run format → lint → typecheck → build → render before a version is ready to publish. Your agent (or you in the dashboard) previews the draft first, then publishes when it looks right.

Anonymous sites skip this: they go live immediately and stay editable for 24 hours. After you claim, drafts and publish apply.

Next: Framework vs static.