This article explains whether you should use Scroll Documents or Scroll Versions for content and versioning.

Scroll Documents and Scroll Versions compared

Here's a quick overview of which features are and aren't

Hosting

TypeScroll DocumentsScroll Versions
Cloud

(tick)

(error)
Server

(tick)

(tick)
Data Center

(tick)

(tick)

Features

FeatureScroll DocumentsScroll Versions

Versioning

Learn more

(tick)(tick)

In-Confluence Publishing

Learn more

(tick)(tick)
Compare changes(tick)(tick)
Conditional content / Variants(error)(tick)

Content reuse

Learn more

(tick)(tick)
Built-in workflows(tick) – on document level(tick) – on page level
Read Confirmations(tick)(error)

Integrations

Scroll Apps

AppScroll DocumentsScroll Versions

Scroll Viewport

Learn more

(warning) Coming Soon

  • (error) Cloud
  • (tick) Server
  • (tick) Data Center
Scroll Translations(error)(tick)
Scroll Exporters
  • Scroll PDF Exporter (tick)
  • Scroll Word Exporter(tick)
  • All Scroll Exporters (tick)

Third-Party Apps

AppScroll DocumentsScroll Versions
Comala Document Management

(error)

(tick)

Difference details

Versioning

Scroll Versions and Scroll Documents use different versioning concepts that come with different strengths and weaknesses. Let's look at a couple aspects:

  • Versioning scope: In Scroll Versions, versions are referred to as Space Versions because they always affect the entire space. In Scroll Documents, any page tree can be a defined as a document, meaning multiple documents each with their own versioning scheme can exist in one space.
  • Versioning approach: In a nutshell, Scroll Versions creates functional child pages – so-called change pages – to store different content for a versioned page. Change pages are only created if actual changes have been made. In Scroll Documents, every version is a separate page tree created during version creation. 
  • Content inheritance: In Scroll Versions, pages that haven't been edited in a given version inherits its content from the version they are based on, meaning changes to that base version will be inherited up the version tree. In Scroll Documents, page content is copied during version creation and exists independently from this point on.
  • Page hierarchy: Change pages in Scroll Versions, are stored as child pages of the so-called master page, which displays different content depending on the currently selected version. For this reason, the position of the master pages in a page tree determines the hierarchy for all versions. In Scroll Documents, the page hierarchy is copied when a version is created, but can be altered in any way, as the page trees are fully separate.
  • Macros compatibilityMany frequently used Confluence macros – for example Children Display – display information based on page tree structure. As the actual page tree in a Scroll Versions managed space is much more complex than is apparent to the user, many base assumptions for macros may not hold true. While we re-implemented many common Confluence macros, any custom or third-party macros might not work as expected. As every version of a Scroll Document is a separate page tree, the app works much closer to what is expected from unaltered Confluence.

In-Confluence Publishing

Both Scroll Versions and Scroll Documents support publishing content from an internal authoring environment to where the target audience can access and read it.

  • Scroll Versions supports publishing to a new space, which creates a standard Confluence space with the content of one version and to an existing space, which updates a space previously published to a new space. In addition, there is the option to publish to the same space, which publishes the content in a Public View within the authoring space.
  • Scroll Documents supports a similar work flow with its Copy and Replace features. Copy can be used to first copy a document or a version of it into a new location. Later, an updated version of that document can be copied to that same location and replace the existing copy.

Content Reuse 

Both Scroll Versions and Scroll Document support content reuse functionality. While Scroll versions takes a more sophisticated approach, Scroll Documents provides a simplified alternative.

  • Scroll Versions enables you to create Reuse Libraries and associate them with specific versioned spaces. You are then able to include the content in your documentation using the Include+ macro. Learn more
  • Scroll Documents enables you to add existing pages to your documents using the Document Composer.  You can either choose to copy content into your document or include them to always reflect the latest content of the included page. Scroll Documents also supports versioning of documents that contain included content. 

Scroll Viewport Integration

Scroll Viewport is K15t's dedicated app for web-publishing content authored in Confluence.

  • Scroll Versions integrates with Scroll Viewport for Confluence Server and Data Center. An enabled integration in a versioned space allows to select which versions are available to the reader in the version picker.
  • Scroll Documents will soon integrate with Scroll Viewport for Confluence Cloud. A document with any number of its versions can be selected as the content source for a Scroll Viewport site. After site generation, those versions will be available to the reader in the version picker.

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 help@k15t.com and describe your needs and use case, and we'll further explain which is the right app for you.