Save & publish

Blok separates saving (drafts) from publishing (what visitors see). This lets you iterate on a page without affecting the live version.

Save — drafts

Press ⌘/Ctrl+S or click the Save button in the top bar.

The current document is sent to your app’s save handler.
The status dot turns green.
The document is not visible to the public yet.

Save is safe to use often — it’s what you’d do after each meaningful change. There’s no separate “autosave” toggle; just save whenever you pause.

Publish — go live

Click Publish in the top bar.

The current document is sent to your app’s publish handler.
Your live page updates immediately (or after your CDN revalidates).
Pre-publish gates run first — SEO readiness, unresolved comments, custom checks. If any error-level gate fails, publishing is blocked.

Publish always implies save. You don’t need to save before publishing.

Schedule publish

From the Publish menu, pick Schedule to publish at a future time. Your app decides how scheduling works — Blok fires an onSchedulePublish event with the current document and the requested time.

Unpublish

From the Publish menu, pick Unpublish to retract the current live version. Visitors will see whatever fallback your app provides (404, coming-soon page, etc.).

Status indicators

The top bar and Publish button together show the current state:

State	Meaning
Draft — unsaved	Changes exist that haven’t been saved. Yellow dot.
Draft — saved	Last save matches the document. Green dot. Not yet live.
Published	The current document is live on your site.
Published — dirty	You’ve edited since the last publish. Yellow dot.

Preview

If your developers configured a previewUrl, the viewport bar shows a Preview icon. Click it to open the live preview of the currently saved draft in a new tab — useful for sharing link-to-draft reviews.

Open published

If the document is already published, an Open Published button in the Publish menu opens the live URL. You can also view the exact JSON of the published version from the Tools panel.