Version History
[Coming Soon]
Never lose your work. Roll back to any previous version with one click.
Version history will track every meaningful change to your landing page, letting you compare versions side by side and revert to any previous state instantly.
What it will do
Every time you make a change through the chat editor (or visual editor, when available), HolyShift will save a snapshot of your page. Version history will let you:
- Browse all versions — see a timeline of every change you've made, with timestamps and descriptions of what changed
- One-click revert — restore any previous version instantly. Your current version is saved before the revert, so you can always undo it
- Before/after comparison — view two versions side by side to see exactly what changed between them
- Named versions — mark important milestones (e.g., "before redesign," "approved by team") for easy reference
Expected capabilities
- Automatic snapshots on every chat edit
- Manual save points for marking important states
- Visual diff showing added, removed, and modified sections
- Revert without losing your current version
- Works across both chat and visual editing modes
Why it matters
Landing page iteration is inherently experimental. You try a different headline, rearrange sections, change the color scheme — and sometimes the previous version was better. Without version history, you'd need to remember what you had or try to recreate it from memory. With version history, you can experiment freely knowing that any previous state is one click away.
Current alternative
Today, you can undo recent changes by telling the chat editor "undo that" or "go back." For changes made further in the past, you can describe what you want to revert to: "go back to the version with the blue hero." The AI does its best to reconstruct previous states from conversation history, but it's not as reliable as a true version history system.
What's next
- Chat editing — the current editing workflow
- Live preview — check your page before and after changes
- Publishing — publish when you're happy with the current version