Versions and Documents Compared
This page aims to answer the question of whether your existing Scroll Versions workflow on Confluence Server or Data Center can be migrated to Confluence Cloud, as some of the features have yet to be implemented in Scroll Documents and some already implemented ones work differently.
The feature comparison below is updated regularly as we continue development on Scroll Documents. The current information reflects the feature state of .
Legend: – Available | – Unavailable | – Partially available
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.
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.
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
Scroll Versions integrates with Scroll Viewport on Confluence Server only, while Scroll Documents integrates with Scroll Viewport on Confluence Cloud only.
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.
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.
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.
Integrate Confluence Server apps with Scroll Versions.
REST API (unofficial)
Use REST resources for process automation.
Scroll Viewport (for Confluence Server/DC)
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.
Still unclear? Please reach out to us
If it's still unclear to you whether or not Scroll Versions or Scroll Documents is right for you, please reach out to us via firstname.lastname@example.org and describe your needs and use case, and we'll further explain which is the right app for you.