Versions and Documents Compared

Cloud

Server

Data Center

Versioning

Create and manage different versions of your documentation in Confluence.

Although both apps provide functionality to create and manage versions of your documentation, there are still some fundamental differences between them that you should be aware of. To learn more, see: Feature Differences In-depth

Variants and Conditional Content

Create and manage different variants of your documentation. 

Both variants and conditional content have been released for Scroll Documents and are supported by the automated migration. To learn more we recommend reading: Conditional Content Macros after Migration

Publish in Confluence

Publish the documentation from your private authoring space to a public space.

Scroll Versions supports three different mechanisms to publish content within Confluence: Publish to a new space, Publish to an existing space, and Publish within the same space. Scroll Documents does not support all these mechanisms yet.

Publish to the Web

Publish your documentation and its versions to a publicly available Help Center using Scroll Viewport

(Server and Data Center)

(Cloud and Data Center)

Scroll Versions integrates with Scroll Viewport on Confluence Server and Data Center, while Scroll Documents integrates with Scroll Viewport on Confluence Cloud and Data Center.

Publish to a Document

Publish your documentation and its versions into different file formats with Scroll Exporters.

Scroll Versions integrates with all of our Scroll Exporters on premise. Scroll Documents currently integrates with all Scroll Exporters available on Confluence Cloud.

Publish to a different Confluence Instance (Remote Publishing)

Publish your content to a different Confluence instance.

As an alternative, you can use Scroll Viewport for Confluence Cloud to publish your documents created with Scroll Documents to a publicly available site.

Content Reuse

To learn more we recommend to also read:

• Feature Differences In-depth

• Include Libraries before and after Migration

Workflows

(basic workflows)

Duplicate Page Titles

Manage duplicate page titles within the authoring space.

The limitation of unique page titles cannot be lifted, it can only be worked around.

With Scroll Versions, this is achieved with the help of the Scroll Page Title which is displayed in page view instead of the actual Confluence page title, which still needs to be unique. The Scroll Page title is used during publishing in Scroll Viewport and Scroll Exporters.

In Scroll Documents, version/language prefixes are used to prevent duplicate page titles within the same space. The prefixes are displayed in page view, but omitted when publishing in Scroll Viewport or Scroll Exporters. If you need to display the same page title within a Document version, you can use the Scroll Page Title property. The Scroll Page Title is only visible in Scroll Viewport, the Document Reader or exports created by the Scroll Exporters. In Confluence the normal page title and the prefix will still show.

For more information about how Duplicate page titles work in Scroll Documents and how they are migrated, see:

• Duplicate Page Titles in Scroll Versions and Scroll Documents

• What Happens to Duplicate Page Titles During Migration to Scroll Documents?

• How Can I Have Duplicate Page Titles Within the Same Version?

Page Keys & Context Sensitive Help

Assign page keys to specific pages that can be used to link to that page.

Page keys renamed to Context Keys are available in Scroll Documents and Scroll Viewport for Cloud.

Java API

Integrate Confluence Server apps with Scroll Versions.

REST API (unofficial)

Use REST resources for process automation.

Scroll Viewport (for Confluence Server/DC)

(Server and Data Center)

(Data Center)

Scroll Viewport (for Confluence Cloud)

Scroll PDF Exporter

Scroll Word Exporter

Scroll HTML Exporter

Legacy Scroll Exporters (DocBook, EclipseHelp, EPUB, CHM)

Comala Document Management

Integrates versioned spaces with Comala Document Management Workflows.