Version management in Paligo consists of three main parts. Revision control, branching, and release management. Let's take a look at all three of these one by one. Every piece of content in Paligo is saved as a revision. This means every paragraph, every image, every topic, and every publication are all automatically saved as a new revision every time they are changed. For example, if this paragraph changes and is saved before and after, this creates two revisions of the paragraph that Paligo tracks in the background. If you ever want to compare two revisions to see what changed, Paligo lets you look at the two revisions side by side. You could also restore past revisions if you want to bring back a previous version of the content. Branching can be a complex topic, but Paligo makes it simple. Let's say you have a version of a topic that you want to stay in place while you work on the next version of it. This would be a perfect situation for creating a branch. You can do this from the context menu. After you have created the branch, you can start authoring the branch and make all the changes you need without affecting the previous versions of the topic. Once you have modified the branch and you are happy with that version, you could either keep the branches separate in parallel with the original or you can merge the branch with the original. Release management is also an easy process in Paligo. Whenever you change the release status of a publication to released, it creates a new version number. This can be helpful when keeping track of the various changes of your content. You can also use snapshots, which are useful for comparing the content between different versions or for restoring previous versions of content. By comparing a snapshot from before and after an assignment, you could easily visualize the changes made to the documentation. You have a lot of content to manage but Paligo's versioning capabilities will make it that much easier.