Documents and versions
In Unfurl, a document is a container with a stable identity and one permanent share URL. You never create a new URL when you revise content — you add a version.
Each time you publish, Unfurl stores a new version: the HTML snapshot, a timestamp, and an optional note. That publish becomes what recipients see on your live share link immediately.
How versions chain
You work forward in time. Version history is append-only: older snapshots are kept for audit and for agents that call get_document.
What the dashboard shows
The document detail view shows a version count (for example v4) and recent publish times in a tooltip. For the full version list with notes and HTML, use get_document from MCP or the REST API.
Going back to older content
There is no separate “rollback” button today. To restore an older snapshot on the live link, publish again with the same document_id and HTML from the version you want, plus a note (for example “Restore pricing from v2”). That adds a new version at the end of the timeline without deleting history.
Use short version notes (“Pricing update”, “Legal review”) so you can scan history months later.
What to remember
- One document → one permanent URL.
- Every publish → one new version (timestamp + optional note) and updates the live link.
- Full history is available via API; the dashboard focuses on the current preview.
