Managing Multilingual Content with Navitabs - Navigation Macros for Confluence

System

Confluence Cloud

Short Description

Organize and manage multilingual content on a single Confluence page using Navitabs—Navigation Macros for Confluence. This simplifies workflows and makes managing multilingual materials easier.

While Translations for Confluence is ideal for users who want to see content in their preferred language while working in Confluence, Navitabs is better for creating multilingual content to share outside of Confluence and organizing content with a clean layout that’s easy to navigate. It’s also helpful for teams that must keep everything in one place during the creation and editing process.

Challenge

Content creators, like marketers and documentation teams, often struggle to manage multilingual content effectively in Confluence. They must create multiple pages for each language or navigate clunky workflows. This approach leads to inefficiencies, scattered content, and difficulty maintaining consistency across translations.

Actors

📝 Jamie – Content Creator / Knowledge Manager
📣 Marc – Marketing Specialist

Actors’ Goals

• Jamie wants to create multilingual document versions in one place to ensure consistency and clarity during the editing process.

• Marc needs to prepare materials in different languages for customers in various regions and manage them efficiently.

Implementation Details

1. Macro Configuration:

   • Use the "Tab Group" macro to organize content or Tab Wizard “Create Your Own Macro” to ensure consistent formatting for tabs.

2. Optional Translation Integration:

   • If the team uses Rovo for translations, they can easily copy and paste the translation from the Rovo chat to the macros

   • If the team uses Atlassian Intelligence, they can easily translate the text they need within the Tab Group (only).

Use Case Scenario (Step-by-Step)

1. Jamie utilizes the "Tab Group" macro to organize content by language systematically. Within this macro, she can use Atlassian Intelligence for translations or the Tab Wizard to "Create your own macro," allowing her to create various text versions.

2. Jamie adds tabs for each language. For example, she creates separate tabs for English, German, and French content.

3. Jamie inserts the translated content (there are different options: For Cloud, Enterprise, and Premium via Atlassian Intelligence feature “Translate”, for all other use cases use your fav translation tool like Deepl, Google Translate etc…)

4. Marc reviews the page. He can easily switch between tabs to compare and review the translations side-by-side.

Outcome

• For Jamie and Marc:

  • They can create, organize, and maintain multilingual content without duplicating pages.

  • Reviewing and editing translations becomes easier with a side-by-side structure.

• For the company:

  • Content workflows become more efficient, saving time and reducing the risk of inconsistencies.

Content