Document Versions: A Checkpoint Before Your Next Big Rewrite
Keep a deliberate checkpoint and restore the document from its saved collaborative snapshot.
By David Hemphill ·
A document's history needs more than a label saying it used to be different. Livemark lets you capture a version and return to it, and restoration now uses the saved collaborative snapshot rather than rebuilding the document from its Markdown.
That matters when you want a checkpoint before a substantial rewrite. Save the draft you have agreed on, try a different structure, and keep a clear route back if the experiment does not work. Restoring should recover the saved document's structure, not merely produce text that looks similar after another conversion.
Versions are deliberate checkpoints. They are not a claim that every keystroke becomes a separately named entry, and they are not the same as deciding whether an individual proposed edit should land. Use a version for a document-wide point in the work; use the change's own controls when you are dealing with one edit.
Before reorganizing a draft or handing it to another collaborator, open the document and create a version from its version menu. Give yourself something concrete to return to.