Saving and versions
Understand saved versions, automatic saves, and the state open in your editor.
A version records the state of your project's files. You can keep working after a version is saved, then save another version or return to an earlier one.
Open version history
- Open your project in the editor.
- Select Publish in the editor header.
- Find the Drafts and Published lists. Select a version to inspect its changes.
To load a version into the editor, use Restore this version in its details. See Return to a version before switching.
Understand the version labels
| Label | What it means |
|---|---|
| Not versioned | Your current files contain changes that are not yet recorded in a version. |
| Drafts | Saved working versions. |
| Published | Major versions created through publication. Check the Live label to identify the version actually serving visitors. |
| Current | The version loaded in the editor. |
| Live | The version currently live on your website. When the same version is also current, the list shows Live. |
Saving a version records your current files so you can return to them later. It does not update the live website.
Save a version now
- In the editor header, open Publish.
- If Not versioned appears, select Commit new version.
- Wait for the new version to appear in the list.
You can also open Not versioned to inspect the files, then select Commit changes. If saving fails, resolve the reported problem and try again before relying on that state as a saved version.
Why automatic versions appear
Reforma can create an Autosave version after a period of inactivity when project files have changed. To keep a particular state before continuing, save a version yourself.
Reforma also maintains project support files and dependencies. These updates may appear among saved changes even if you did not edit those files yourself. They do not necessarily mean a teammate edited the project.
Undo, discard, or return to a version
Use Undo and Redo in the editor header to step backward or forward through editing actions.
Returning to a version loads all project files as they were at that point. See the restoration example for how this affects later changes.
Revert changes discards all unversioned changes since the loaded version. It creates no saved version and cannot be undone. Follow the discard procedure only when you want to remove that work.
Which versions can I return to?
You can restore another saved version while it remains in the list. Switching versions keeps saved history, so you can return to a later saved state as well.
Publication changes draft history
Publishing clears draft entries, including newer drafts if you publish an older state. Check the warnings in Publish and update before proceeding.
Version history covers project files. Returning to a version does not restore data stored in external services.