Content Reuse with Versions
In this article, we'll look at how you can reuse content in Scroll Versions and Scroll Documents respectively. By understanding the differences, you'll get a clearer picture of how each app handles content reuse.
Reuse Content in Scroll Versions
With Scroll Versions and Scroll Translations, you can reuse content from other versioned or translated spaces by creating an Include Library. This setup links two spaces:
one for writing,
and one for storing reusable content.
You then use the Include+ macro to embed this reusable content into your documentation.
There’s also an Excerpt Include+ macro, which allows you to include excerpts, but only from pages within the same space.
When transitioning to Scroll Documents, this reuse model changes slightly. During conversion:
Pages previously included from other spaces are copied.
These are placed under a parent page called _SvIncludeLibrary.
If the content was reused in multiple spaces, the same content is copied into each converted space.
To learn more about what happens with a converted Include Library, read: Conversion with Include Libraries
Reuse Content in Scroll Documents
In Scroll Documents, you can use Confluence’s standard include macros to reuse your content.
You can reuse content using two main strategies:
Separate include library space: Create a dedicated Confluence space (without Scroll Documents) to host shared content. This is useful when multiple documents in different spaces need access to the same reusable content.
Include within the same space: Create an _Include page directly in your Scroll Documents space. Place this page above the root page of your Scroll Document and add all reusable content. This structure makes it easy to find and version reusable content.
You can version your included content in Scroll Documents using the resolve inclusions option, ensuring that the content remains static in saved versions
If you want to learn more about reusing content in Scroll Documents, you can read the following articles: