Some content on Refined sites is automatically translated for visiting users, based on their Atlassian profile or browser settings. Some content needs to be translated manually, if you want a site to be fully available in another language.
If a language isn’t available for automatic translation, the language defaults to English.
Content | Manual or automatic translation? | |||||
|---|---|---|---|---|---|---|
Non-editable (hard-coded) text in Confluence/JSM headings, menus, etc | This is automatically translated based on the user’s Atlassian profile language settings. | |||||
JSM request types | Manually set up translations in the JSM project’s settings. The language on the Refined site then follows the user’s Atlassian profile settings. | |||||
Non-editable (hard-coded) text in Refined site menus and buttons. | This is automatically translated based on the user’s browser language settings.
| |||||
Editable text:
| Refined doesn’t offer automatic translation and isn’t compatible with third party translation apps from the marketplace. You’ll therefore have to create content manually in every language that your sites will contain. We’ll explain how to do this in the guides below. |
Recreate a site in a different language
Because manual translations are needed for content such as landing pages and navigation menu items, you can best serve audiences in multiple languages by creating one site per language. In this tutorial we assume the site contains both Confluence and JSM content, but of course you can skip the instructions that aren’t relevant to your site.
Build a Refined site in a single language. In this tutorial, we’ll create a Dutch translation of our English Octo Support demo site.
Create copies of all the Confluence spaces that you added to the first site, and translate them in Confluence.
Create a new site for the second language.
Apply the same theme to the second site.
Create a similar site structure.
Apply the same site settings to the second site. Make sure to translate settings such as announcement banners and promoted search results.
On the first site, open a landing page. Edit the page and export the page’s layout. Open the equivalent of that page on the second site and import the layout. Translate all content on the page. If needed, update module settings such as links, page IDs, and project IDs. Some dynamic modules like Page Trees pick up on their location on the site and may already show the right content.
Repeat this process for all landing pages on your site.
Create a footer, following the same instructions as in step 6 above.