Best practices

Keep the same language order

Across pages. Your authors edit and review several; a stable order saves them hunting.

Put your most common language first

It is the fallback when a reader's language is unavailable.

Keep pages to a few languages

There is no technical limit, but display time grows with each language on a page, noticeably so beyond a handful. The app marks pages past three languages - not an error, just a signal. Up to three or four keeps the experience fluid; beyond that, ask whether every language truly belongs on this page. Very long, many-language pages are also harder to edit.

Translate the text, not the structure

Identical headings, lists and tables across languages make discrepancies obvious at a glance when updating.

Warn before removing a language

Deleting a macro moves the affected readers to the default language, with no notice on their side.

Changes notify everyone

A change in one language notifies everyone watching the page, and shows in its history. That is normal Confluence behaviour, and it surprises people at first.

The page title

A page's title exists in one language only, shared by every translation - see feature details. Two approaches work well: write it in the team's main language, or give it a short form everyone recognises - a product code, a proper noun, a reference.