Brief overview of how you as an author can work with versioning content in Paligo. To find out all the details, we provide an in-depth demo video (approx 20m long) on Paligo Academy.

What is version management?

Version management in a CCMS is the process of creating multiple versions of a content asset from a single source. This allows you to make changes to the source asset, and then apply those changes to all of the different versions. It also allows you to keep track of the different versions, making sure all versions are up-to-date with the most recent changes. Versioning is an essential part of content creation, and is a core feature of Paligo.

Version management in Paligo consists of three parts:

  • Revision Control: You can view the history of a topic, roll back to previous revisions, and compare different revisions of a component.
  • Version Branching: Branches are parallel versions of content. You can create a separate branch of your content, a publication or a topic, that can live side by side with the original. If needed, you can later merge the content of the two different versions.
  • Release Management: Release versions are linear versions in time of a component. Each time a component changes workflow stages, the release version is stepped up with version numbering, such as “Version 1.0.2” and so on.

The versioning capabilities of Paligo ease release workflow management

​​If you’re working on a version for a product that is still in development, you might have to update documentation frequently. You can create a version of a document or topic that is separate from the original, allowing you to work on different parts while staying within the same project.

Paligo’s workflow has five stages, connected to Release Management.

  1. Work in progress – The initial stage for authoring and editing content.
  2. In review – When the document is in review and proofreading, it is not locked, but marked as “in review”.
  3. In translation – While the text is translating multilingual content , the topic is locked for editing.
  4. In translation review – For proofreading or post-editing translations in the translation editor.
  5. Release – The final version of the topic is locked for further editing, and archived, remaining intact just as it was at that stage.

The benefits of version branching

Version branches are parallel versions of your content. Paligo lets you create a separate branch of a content component, that lives side by side with the original. This is beneficial for small changes to your content, without affecting the main version. Such as:

  • Variations in product models.
  • Creating a localized version of your content, such as for a different language or region.
  • Testing a new approach or format when creating content.
image shows a person working with version management in a single source ccms

What are the key reasons for versioning?

Versioning allows companies to maintain different versions of their documentation in a single source. For example, small differences in product models or procedures. In this way, companies can keep track of changes to their documentation more efficiently, without the need for duplication.

Version management is an important tool for providing accuracy and consistency in content creation. The ability to access previous versions and make modifications if needed keeps all versions secure. Because of this, organizations maintain a well-organized set of content that is up to date and accurate.