How autosave works

The save state sits to the left of Editor tips and Preview. While you type, that spot stays blank. There is no Unsaved label and no Save button.

1. Stop typing. A spinner with the name Saving appears, then the same spot reads Saved. After Saved, the header goes blank again.

2. After Skip for now, the first save creates the row and the address can move from /c/case-study/editor to /c/case-study/editor/ plus the new id. After Upload file, the row already exists.

3. Type in the title or a section body to start a save. Empty, the title shows Untitled.

4. Read Couldn't save — retry when you can click to send the draft again, or Couldn't save when you cannot. Stay on the page. Preview will not open from either error. If Dusted is unsure the last write landed, the header reads Checking whether your changes were saved….

5. If another copy changed this case study, the header reads This case study changed elsewhere. Your draft is still here; refresh when you're ready to load the latest version. Refresh when you are ready.

6. Click Preview to finish the current save first. An overlay reads Turning ideas into something worth sharing. With no content on /c/case-study/editor, a toast reads Add some content first. A save error on an existing row reads Fix the save error before publishing. A failed first save reads Could not create case study.

7. In Preview mode, the save lines leave the header. Publish stays unavailable while a save is in progress. The draft menu reads Draft: plus the title, or Draft: Untitled. Dusted finishes the current save before you switch drafts or click New case study.

If a write is still running or in error when you close the tab, the browser can ask you to stay.

Return to Start a new case study if you still need the path onto this page. Format your writing covers the toolbar.