Manage Versions of Confluence Documentation With Scroll Versions header image
documentation

Manage Versions of Confluence Documentation With Scroll Versions

Expanding the functionality of page versions in Confluence Server and Data Center, the Scroll Versions app introduces the concept of true space versions.

scroll-versions.png

A space version is a collection of pages that have been changed. So your team can manage all changes related to a release of your product, and keep them separate from changes for other releases. In Scroll Versions, you can manage Confluence space versions quickly without the complication that comes with writing documentation for major and minor releases of your product. So what would otherwise involve a manual process of space copying or exporting is instead done with the click of a button.

scroll-versions.png

Content Inheritance

Within Scroll Versions for Confluence you can define space versions for your content, which typically relate to a version of your product. When creating a space version, you set which version precedes the one you're creating. This is helpful for version branching, like for major and minor releases, and also for content inheritance.

versions-screen.png

With inheritance, changes in a version reflect on all subsequent versions. For example:

Let's say you have space version 1.0 for your first major release. You then create space version 2.0, which is based on version 1.0. With inheritance, any changes you make to 1.0 also appear in 2.0. This is particularly handy when making corrections or adding missing content. With inheritance, you don't have to copy the improvements to all future versions; it's just taken care of.

Now, there can be instances where you've updated something in space version 2.0 and then later in 1.0. In this case, the change in 1.0 will not be inherited in 2.0, to avoid overwriting the change in the newest version. This is useful when a part of your product is updated in every version. 1.0 is independent of 2.0. Even when going back and making a correction to space versions 1.0 should only affect that version, since space version 2.0 has been updated to reflect the latest version of the product.

Scheduling Changes

As your team writes in your documentation space, you can schedule the version in which each page change is included. So maybe you made a correction that you want in space version 1.0 and maybe you've added a new section that should only be included in version 2.0. You can schedule these changes using a version picker right in the Confluence editor. You can also reschedule changes at any point.

version-picker.png

With included reports, you can review changes to individual pages, compare the changes to a page across different versions, and see all changes included in a space version.

content-in-version-report.png

Publishing

When you're ready to publish a version, you can publish in a few different ways:

  • To the web by  creating a help center - This is great for sharing your documentation on the web outside Confluence. With Scroll Viewport, you can share the content as an online help center – like this one.

  • To a document  using an exporter - You have the flexibility to share your documentation in different customized file formats. You can customize export templates and export your documentation as a document matching your corporate identity.

  • In Confluence - This is great for authoring and sharing documentation directly in Confluence. When you're ready, you can publish the space version from your private authoring space to a public space.

Learn more about  publishing

Review Process

When working with changes in your documentation, it's important to have the right people on your team review the content to ensure it's accurate. To help with this, Scroll Versions includes workflows, which automatically mark a page as a draft when you're updating it. You can then use workflows alongside Confluence permissions and some predefined roles to move each updated page through the review process and then on for publishing.

Learn more about  automating your workflow.

Learn more about Scroll Versions for Confluence Server and Data Center.

Embed comments

Next Up...

Use Confluence page and space versions to track changes and organize your versions of your content.

documentation
Steffen Burzlaff Steffen Burzlaff

If your team makes a product that's always on the latest version, such as a SaaS app, it may be less important for users to have access to older versions of your documentation.

documentation
Steffen Burzlaff Steffen Burzlaff

Scroll Documents enhances Confluence Cloud by enabling your team to manage and version your documentation collaboratively.

documentation
Steffen Burzlaff Steffen Burzlaff

Another approach to versioning is to use a single space for both authoring new documentation and publishing released documentation.

documentation
Steffen Burzlaff Steffen Burzlaff
Share this article
Reset Cookies

The following services will be reset and deactivated for you.

  • Typeform:
    We're using Typeform to embed quizzes and surveys into our website. By clicking "Disable all services" you're no longer able to submit quizzes or surveys on our website until accepting the service again.
  • Hyvor Talk:
    We're using Hyvor Talk as a comment tool. Hyvor Talk sets a local storage when activated. By clicking "Disable all services" you're no longer able to post or read comments on our website until accepting the service again.

By clicking "Disable all services" all cookies and local storages related to the services will be removed. Before using them on our website again, you need to accept them.