# Saving, publishing, and leaving the editor

URL: https://kywi-docs-production.up.railway.app/editing/saving-publishing-and-leaving-the-editor
Type: docPage

Save changes the public page at once, Save Draft holds your edit for review, and a failed save keeps the editor open with your changes.

This editor only opens on a page that is already live, so every button here acts on a published page. Save Draft and Save are always there; Schedule and Publish appear only if you have publishing rights.

## Save goes live; Save Draft waits for review

Save writes your layout straight onto the page visitors see. There is no review step in between, even if you could not have published the page yourself.

Save Draft is the button that keeps an edit off the live page. It queues the edit as a draft for review, and the public page keeps showing the published version until someone approves it. A newer draft of yours normally replaces your earlier one; it can't while the earlier one is part of a schedule, or when someone else's draft is newer than yours — then both stay in the queue. When you reopen the editor, it opens on the newest pending draft and says when it was saved — unless the live page changed after that draft, in which case it opens on the live page and tells you so.

## Use Save Draft when the edit needs a second pair of eyes

Save is a publish in all but name. If the change should be reviewed before visitors see it, Save Draft is the only button in this editor that guarantees that.

## Publish and Schedule

Publish saves the layout and keeps the page live. Schedule asks for a time first and refuses one in the past; your edit then waits as a draft, and the live page is unchanged until that time. A page has one schedule at a time, so scheduling again replaces the earlier one. Reopen the editor to see the schedule and cancel it; canceling leaves the draft in the review queue.

Outside the editor, the Publish button in the toolbar publishes the page as it is stored, without opening anything.

## When a save fails

A save that does not land keeps the editor open, with the reason just under the edit bar and your changes still in front of you, so you can try again. If someone else saved the page after you opened it, Save and Publish stop and ask which version wins: reload theirs and lose your changes, or overwrite theirs with yours. Save Draft and Schedule don't ask — they only queue a draft, so nothing is overwritten.

## Leaving with work unsaved

Closing the editor stops to ask first whenever there’s something unsaved — it won’t discard edits on your way out without a confirmation. Closing the tab or navigating away triggers the same warning at the browser level, for as long as anything you’ve touched hasn’t landed yet.

## No reload needed after you close the editor

When a save, draft, publish or schedule closes the editor, the page underneath is rendered again from the server. After Save or Publish you see your edit; after Save Draft or Schedule you see the live page, which is unchanged until the draft goes through.
