Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Organizing and displaying content in multiple languages.

My company is moving to Confluence for all of its technical documentation, users' guides, knowledgebase, and the like.

Much of our content is available in multiple languages. English, Japanese, Traditional Chinese, Simplified Chinese, Korean, German, soon to add Portugese and Italian. You get the idea.

We're having difficulty in finding a good way to display this content in a way that keeps each language associated with others of its kind.

Currently, English is our primary language (and represents 85% of our user base). English articles are displayed, with other languages as child pages of the English page.

Unfortunately, this means that a Japanese-speaking customer doesn't have an easy path from his Japanese User Guide to the Japanese Knowledgebase.

Making this more difficult is the fact that management wants to keep the English documents available to users in all languages. Most of our work is done in English first. New KB articles and updates are always in English before they get translated. Management wants all users to have access to English docs easily.

We've had a few ideas:

1) Create a new space for each language:

  • Pros: Every document for a language is with all others of its kind.
  • Cons: Access to English documents is somewhat restricted.

2) Keep all documents in a single space. Create a parent page for each language, make all documents children of that parent page:

  • Pros: Easy access between languages, logical organization
  • Cons: Search may return duplicate entries for un-translatable English phrases/names/terms/etc. Page names can get really long (Product Name User Guide - English - v4.3) which makes lists of content look cluttered.

How do you handle your documentation in multiple languages? Using something similar to the above?

Any examples would be greatly appreciated.

6 answers

1 accepted

5 votes
Answer accepted

Hi Eric

We've had some internal discussions on this - and we came up with the following as the overriding premise:

Spaces are free - so plenty ok to have lots of them over time.

More important is navigation and search as the driving factors. Redundant search results is a deal-breaker, agree. We came up with this, for most flexibility as well as functionality:

  • separate space per doc title, per version, per translation flavor
  • maybe two letter countries in the version, and English not needed.

For example (English, French, Spanish, Chinese):

  • HibicusSoft User Guide, v1.0
  • HibicusSoft Guide de l'utilisateur, v1.0 FR
  • HibicusSoft Guía del usuario, v1.0 SP
  • HibicusSoft用户指南,v1.0 CH
  • HibicusSoft User Guide, v2.0
  • HibicusSoft Guide de l'utilisateur, v2.0 FR
  • HibicusSoft Guía del usuario, v1.0 SP
  • HibicusSoft用户指南,v1.0 CH


Also just as a note - the product name often leads in a document title and is usually not translated, regardless of language (so the docs are grouped by the products in the space list).

We felt this allowed for best of all worlds: no redundant searches, clean organization, and downstream controls on release management of the docs since easy to archive "full spaces" in Confluence (which is a good path if translation and product versioning workflow automation is enabled later).

KB Articles include a different complexity - since they can be short 1-pagers. In these cases, do you really translate each of these? If not - you could try an on-the-fly translation tool - like SpeakMyLanguage, and just retain an English as the primary source - and keep them all in one space. The KB space.

A KB has different needs and requirements than full docs - so maybe you'll want some custom functionalities for managing these, ratings, feedback, etc. All possible - just need to plan out your critical requirements, and suggest to be done somewhat iteratively as you grow and evolve this.

And what about export requirements? Will you also need PDF versions of the docs? Scroll PDF Exporter is the trick. And well worth it! It does ALOT, easily.

Other thoughts:

  • I think Atlassian organizes their doc pretty orderly - so just roll the translation flavors in with that.
  • Also - Sarah Maddox's book is a must have while you are figuring out this process - for these considerations and more, in terms of managing tech doc in Confluence. Worth every penny - Get it.
  • Zen Foundation also would be good for some instant look and feel theming, among other, that will greatly improve the user experience. Zen also provides some nice navigational macros that could help alot.

There's lots of ways to do this - but these are some simple ideas for starts.


I think you are not alone in this, as Confluence is used for documentation more and more in technical communications.

We'd love to talk to you about your situation if you'd be keen to reach out -


I'm going to bookmark this answer. There's a lot of good info there.

I'll definitely talk to my team about SpeakMyLanguage. Translation is a big timesink.

We've dabbled (well more than dabbled - have a PoC, but not released) with an Enterprise Translations for Confluence plugin, that addresses the doc portion of the story I wrote -

But time has evaded us to get it out. Been a busy summer. Not lost in desire -

Love if you would like to be our test subject (on staging servers) - since we want to work with a customer that has LOTS of languages to play it out for real. And a clean, simple, repeatable, and reliable process built into the solution is a big part of it.

I have not a doubt in my mind that it would save your corp many many many many 1000s of $$, over and over again.

Here's another great link I found - roll-up of good write-ups, resources, etc.

Dear all,

bitvoodoo's app "Language Macros" has been mentioned in earlier answers. As the technical writer at bitvoodoo, I'd like to inform you that we've made some major improvements to our app since 2013 :-) 

It is now called "Translations for Confluence", available for Server & DC (and Cloud, since April 21):

The app now also translates page titles, which will then be used in the page tree, breadcrumbs, search, etc.

I just published a blog post on the subject as well:

Don't hesitate to reach out if you need more information.

Best, Cora

We've had issues with Service Desk and Confluence Cloud support for multilanguage that can't be solved by any cloud add-on we could find. We have opened tickets about it linked below and would appreciate the support if you agree.




for what you are looking for, our Language Manager Plugin for Confluence seems to be a good fit. You can also check it out directly on the Atlassian Marketplace, of course. 

It lets you connect pages in multiple languages, it has no restrictions on languages or language packs. One idea behind it is, to only translate your important content.

Once installed, you can access the Language Manager from any page in Confluence. Multinational organizations really love to work with it.

Hi Guys,

Could you please recommend me a great commmercial plugin for supporting technical documentation in different languages, including English, French, and Dutch? I tried some freeware,, but it fails to support pagetrees and TOC in other languages.

Your advise is much appreciated!


Hi @Olha Vdovych,

have you already had a look at Scroll Translations for Confluence?

With that you can easily manage and translate multiple languages within a single space - you can translate the content, but also the pagetitles, which means the pagetree is also displaying the translated content.

Scroll Translations allows you to translate your content either directly within Confluence, but is also compatible with external Translation Management Systems.

You can export your content within a couple of clicks, import it to your TMS, translate it externally and then re-import it back to your Confluence system.

Hope that helps. If you have any further questions, please let me know.



Hi Nils, thank you for that answer. Do you know if a cloud version will be released soon ?

Hi Kilian,

Thanks for your interest in Scroll Translations.
There are no short-term plans to bring Scroll Translations to the Cloud, however we're tracking this requirement in our Jira system: Confluence Cloud Compatibility.

If you want you can sign up at!default.jspa to watch, comment on or vote for this issue. We'll then send a notification for every status update.

Giving the fact that Scroll Translations supports both, manual in-Confluence translation, and has an integration with external Translation Management Systems - what would be your ideal way of translating the content? Do you have a TMS in place, or would you rather translate manually?


Hi Nils, 


Thank you for your answer !

I would say : automatic external translation first + manual corrections but I can't say it precisely until we use it.

waiting for a cloud version I use now a tab builder, Confluence macro Navitabs



Hi Kilian,

Thanks for the details. I'll make sure to let you know as soon as there are any news about a potential solution for Confluence Cloud.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events