An archive keeping every version of your website. Every change is traceable and any earlier state can be restored.
There's one file on a laptop. If it's gone, the website is gone.
Any version from the past years can be brought back in minutes.
- Every change is recorded on its own
Who changed what and when is settled. This isn't a backup, it's a chronicle.
- Work happens on side branches
What isn't finished can't disturb what's running.
- Merging is its own step
A branch only reaches the main line once it has been reviewed.
- Back to any earlier state
Every point in the history can be restored — including last month's.
- Working state
- Own branch
- Review
- Main branch
New work grows on a side branch. The main branch — the one that goes live — stays untouched until something is finished.
An archive built on Git. Every change is recorded as its own entry, with time, reason and the full state of the project. You can return to any of those points, even years later.
- Base
- Git
- Unit
- one entry per change
- History
- complete
- Handover
- the archive goes to you
Every change recorded, with date and reason
If something doesn't work, I step back one version
On handover you receive the complete archive
It backs up the project, not your content. Anything in a database — appointments, enquiries, customer data — needs its own backup.
Each project has its own archive — including what you'd take with you if we stopped working together.