Undo and Version History
Every change is preceded by a snapshot. Undo restores the newest one.
Webby keeps a running history of each page. Before anything changes it — a rewritten section, an added block, a reorder, a delete, a save of your own typing — the page as it stands is recorded.
That history is what Undo uses, and what Versions lets you browse. It is per page, it survives closing the tab, and it does not care which browser you are in.
Steps
Undo the last change
Undo in the toolbar, or Ctrl/Cmd + Z, puts the page back to how it was before your most recent change.
Because it restores a recorded version rather than replaying something held in your browser, it works after a reload and it works on changes made in a previous sitting. It takes a moment and the preview reloads, which is the visible cost of it being real.
Redo, or Ctrl/Cmd + Shift + Z, goes back the other way. Making a fresh change clears the redo direction, as you would expect.
Open the version history
Versions lists every recorded point for this page, newest first, with how long ago it was, what kind of change it preceded, and the instruction behind it where there was one.
That instruction is what makes a long history readable. Before structural edit: lead with the migration support tells you what you are looking at in a way a timestamp never will.
Preview before you restore
Selecting a version renders it, so you are looking at the page as it was rather than guessing from a label.
Do this. A history of twenty versions is hard to navigate from descriptions alone, and the one you want is often not the one you first reach for.
Restore it
Restore this version makes it the current page.
Restoring is itself recorded: the state you are replacing is snapshotted first, so restoring the wrong version is recoverable. You can always get back to where you just were.
Know what is recorded and what is not
A snapshot is taken before: asking for a change to a section, adding a section, duplicating one, deleting one, reordering, editing the page's CSS or JavaScript, saving your inline edits, and restoring a version.
What is not recorded is a change you have typed but not saved. Until you press Save, your typing exists only in the browser — and it is the save itself that creates the restore point.
Tip: Before a big experiment, save. It costs nothing, takes a second, and gives you a labelled point to come back to if the experiment goes nowhere.
Result
The page back at a state you chose, with the state you left recoverable too.
