Content and editing
Drafts and revisions
Recover work without silently overwriting a newer edit.
On this page
Browser and server recovery
Browser recovery stores a local recovery copy independently of server drafts. For saved pages, private server drafts are written after roughly five seconds without an edit. They belong to a user/page pair and remain available for seven days. An existing recovery draft pauses automatic replacement until you restore or discard it. Unsaved new pages rely on browser recovery until their first save. Clearing browser storage can remove that local copy.
Saved revisions
Normal saves create revisions. The service keeps at most 30 revisions per page within a 20 MB page-history budget, while preserving the pre-upgrade content on its first edit where applicable. Loading a revision populates the editor for review; it does not publish by itself. Save only after checking the restored content and layout assignments.
Conflicting edits
Each page has an optimistic version number. If another session has saved a newer version, stale writes are rejected rather than overwriting it. Keep your recovery copy, reload the saved page and reapply the intended changes. Private history responses are not publicly cacheable. Draft endpoints cannot publish pages, change roles or provide an external authoring API. They require the editor session and CSRF protection for mutations.
Recoverable fields
Current snapshots include title, description, body content, legacy footer content, shared header/footer selections and article category. A history snapshot is not a backup of media files, user accounts, provider connections or deployment configuration.
Something unclear? Contact me about this guide.