Saving and revisions
Handle optimistic concurrency, recover drafts and separate save from publish.
Two different versions
document.version identifies the serialization format. page.version identifies the saved page revision. Use the page revision as expectedVersion when saving. Never substitute the document format number.
Save sequence
- Load the latest page and retain its version.
- Edit the document without discarding unrelated fields.
- Save with that expected version.
- Check the returned status, not only the HTTP status code.
- Retain the returned new version and read back important changes.
The save operation can return a conflict result even when the HTTP request itself succeeds. On conflict, reload and reconcile the edits; an automatic blind retry risks replacing another person's work.
Restore a revision
The client adapters expose listRevisions and restoreRevision. Inspect the target revision, confirm the intended recovery with the user, then reload after restoration. Keep preview and publishing as separate verification steps; do not assume restoring a draft republishes the site.
Operational recovery
Revision history helps recover editing mistakes but is not a database backup. Maintain PostgreSQL backups and test restores as described in deployment.