In Helpjuice, Versions and Revisions help you track changes in your articles over time. Versions allow you to manage major changes or separate variations of an article, while Revisions capture each saved change within a version. This article explains how these features work, how to use them effectively, and how to restore previous states.

In this article, you’ll learn:

• What Revisions are and when they’re created
• How to compare revisions within the same version
• How to restore past revisions
• What Versions are and how to create new ones
• How to access published and older versions of an article

What is a Revision

A Revision is a saved state of an article within a specific Version. A new revision is automatically created whenever you:

• Make changes and save the article as a draft or publish it
• When autosave triggers

Viewing Revision History

• Open your article in the editor
• Click on More (…) → Revision History to see all revisions under the current Version

Comparing Revisions

You can compare the current revision with any previous revision within the same Version.

• In the Revision History, locate the revision you want to compare to the current one
• Click Compare with Current Revision

Restoring Revisions

If you want to revert to a previous state, select the target revision in the Revision History and click Make Current Revision to restore that revision as the active one.

What is a Version

A Version represents a major iteration or variation of an article. Each Version has its own set of Revisions. Versions help you maintain separate drafts or different published states.

Creating a New Version

• Click the Status Manager in the top right corner
• Select + New Version

After creating a new Version, when you edit a published version, Helpjuice will maintain the published Version untouched while you work in draft mode within the new Version.

If you edit a published Version, a new draft Version will be created to track those changes before publishing.

Managing Published Versions

• The main article URL (e.g. yoursubdomain.com/article) always shows the default published Version.
• Other published Versions are accessible via their direct URLs (for example: yoursubdomain.com/article/version/2).
• If multiple Versions are published, the most recently published Version becomes the default shown at the main article URL.
• Republishing an older Version will replace the current default Version and become the new default.

Examples / Use Cases

Use case 1: You have a product documentation article that needs seasonal modifications. Create Version A for the standard content, then Version B for seasonal updates. Revisions in each Version track ongoing edits.

Use case 2: After publishing a Version, you receive feedback that content needs to revert to a prior state. You locate the previous revision within the same Version and restore it.

Best Practices

• Use Versions when making major content changes (e.g., for seasonal content, significant rewrites, or versions for different audiences).
• Use Revisions for smaller edits and updates (typos, updates, incremental changes).
• Regularly review Revision History to recover accidentally deleted or overwritten content.