Publishing

Environments

A workspace starts with Production only. Add Staging, or a per-team preview environment, in Settings → Environments. Each has its own public key, its own published content, and its own cache.

Protected environments require an approval before anything reaches them.

Publishing

Publishing takes the current draft and copies it to the environments you pick. It is a copy, not a build: the same bytes that were reviewed are the bytes that go live, and the cache purge is part of the same operation. A page is live in under a minute, usually a few seconds.

Versions

Every publish and every manual save (⌘S) writes a version. The history drawer shows them with who and when. Clicking one previews it on the canvas rather than applying it, and restoring goes through the normal edit path, so ⌘Z takes it back. Looking at an old version can never cost you your work.

Approvals

Authors can edit but not publish. Their primary action is Submit for review, which notifies the workspace's approvers. An approver sees the change summary and either publishes it or sends it back with a comment.

Scheduling

A publish can be dated. The Worker's cron checks each minute for anything due and publishes it with the same code path as a manual publish, so a scheduled release behaves identically to one someone clicks.