Version control is a system for keeping a history of changes to files. Rather than saving copies named site-final-v2-REALLY-final, every edit is logged with a date, an author and a reason, and any earlier state can be brought back. It is also called source control, and the software that does it is a version control system, or VCS.
The problem it solves
Without it, two people editing the same site overwrite each other, nobody knows which copy is current, and a bad change can only be undone if someone happened to keep a backup. Version control answers three questions at any moment: what changed, who changed it, and what did it look like before.
Centralized and distributed systems
Older tools such as Subversion (SVN) are centralized: one server holds the history and everyone checks files in and out of it. Distributed systems, led by Git and also Mercurial, give every developer a full copy of the history, so work continues offline and any copy can rebuild the server. Git is now the default choice for almost all web projects, usually hosted on a service like GitHub.
Whatever the tool, the core ideas are the same: a repository holds the project, each saved change is a commit or revision, and branches let separate lines of work proceed in parallel until they are merged.
Version control you already use
Google Docs' version history and the "restore previous version" button in many website builders are simple forms of the same idea. Developer version control goes further: it tracks thousands of files together, lets two people change different parts at once, and records an explanation for every step.
A practical scenario
A café updates its menu page and, in the same session, a developer tweaks the page template for mobile. The next morning the menu prices display in the wrong currency. With version control, the developer can compare the page against yesterday's version line by line, see that the currency setting was changed in the template commit, and reverse only that change while keeping the new menu.
When a small business should care
If your site has custom code, insist that it is kept under version control in an account you own. It is your insurance against a developer disappearing, a bad update or a dispute about what was delivered. If you only use a drag-and-drop builder, check that it offers some version history, and know how to restore from it.
Version control mistakes
- Treating it as a full backup. Version control covers code, not your database, customer uploads or email.
- Tracking secrets. Passwords stored in history stay there even after the file is edited.
- Editing the live server directly. Changes made over FTP on the server bypass the history and get overwritten by the next release.
Related terms
- Git: the most widely used version control system.
- Repository: the store of files and history.
- Commit: one recorded change.
- Deployment: releasing a chosen version to the live site.