Publish Translations
This article outlines how publishing options differ when moving from Scroll Translations (and Scroll Versions) to Scroll Documents and its extension apps.
Use cases
Scroll Documents and its extensions are optimized for:
If your use case isn't fully supported, feel free to contact us at help@k15t.com — we’d love your feedback.
Publishing Options with Scroll Translations
With Scroll Translations, you can publish content in multiple ways:
Online help center: Use Scroll Viewport to deliver content to an internal or public site—on its own or with Scroll Versions.
Offline manuals: Export content to PDF, Word, or HTML using the Scroll Exporter apps.
Multilingual intranet: Publish translated content to a new space or manage it within a Scroll Translations-enabled space.
Publishing Options with Scroll Documents
Scroll Documents supports similar publishing workflows for translated content:
Online help center: Use Scroll Viewport to create a user-friendly, multilingual help center with language picker support.
Offline manuals: Export translated documents to PDF, Word, or HTML using Scroll Exporters.
Multilingual intranet: Publish translations within Confluence to a separate target space, or keep all translations directly within the authoring space.
Key Differences for Multilingual Intranets in Scroll Documents
If you're converting from Scroll Translations to Scroll Documents for a multilingual intranet, here are the key changes to be aware of.
Publishing to another space
When publishing languages to another target space with Scroll Documents, keep the following changes in mind:
Single-language publishing: Only one language can be published at a time to the same space.
Prefixes required: To publish multiple languages to the same target space, use prefixes to distinguish each language’s page tree.
No language picker: In the target space, users navigate by selecting pages in the page tree—there’s no integrated language picker.
For better navigation experience, publish each language to its own space.
Publishing within the authoring space
When keeping the languages within your authoring space with Scroll Documents, keep the following changes in mind:
Separate page trees per language: Each language gets its own structured page tree.
Language picker available: Readers can switch languages using the picker in the Document toolbox.
Summary
Below is a summary of the similarities and differences we’ve listed above:
Publishing Scenario | Scroll Translations | Scroll Documents |
|---|---|---|
Online help center | Supported via Scroll Viewport | Supported via Scroll Viewport |
Offline manuals | Export to PDF, Word, or HTML | Export to PDF, Word, or HTML |
Multilingual intranet | Publish one or all languages to a single target space, or manage them within the authoring space. | Manage all languages within the authoring space, or publish each language to separate target spaces. |
Language picker in Confluence | A language picker is available in the Scroll navigation bar within the authoring space and in the published space (if multiple languages have been published). The page view automatically updates based on the selected language. | If languages are kept in the authoring space, a picker is available in the Document toolbox. When published to another space, no picker is available—users must navigate via the page tree using language prefixes. |