Paligo has version control that is well adapted to the way technical writers work. Instead of having to handle conflicts, as in some version control systems, Paligo locks a file when it is checked out by someone.
The Version Management in Paligo consists of several parts:
Revision Control - This is the edit history of textual content. You can view the history of a topic, for instance, roll back to previous revisions, and compare different revisions of a component. Every time you save a component, Paligo stores a record called a revision.
Branching - Branches are concurrent / parallel versions of content. It means you can create a separate branch / fork of your content, a Publication or a topic, that can live side by side with the original.
It is similar to a copy, but with more features. A branch "knows" that it originates from another version, and if needed, you can later merge the content of the two different versions.
Release Process - Release versions are linear versions in time of a component. Every time a component changes workflow status to Released, the version is stepped up, either a minor or a major version, with version numbering, such as "Version 1.0.2" and so on. Also, a snapshot is automatically saved and archived.