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. History is append-only; old versions stay.
• 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.
• 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.