Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
This page helps you choose the appropriate structure for a multilingual site. You typically have three choices for organizing content: single tree, multiple trees or a mix of the two.
Magnolia can store multilanguage content in a single JCR content node. This means you only need one site hierarchy. A single tree stores each translation as a property under the same parent node. See Storing localized content for an example what the repository hierarchy looks like.
As long as your site content is reasonably similar from one language to another, this is the best option. You will have fewer pages to manage and the system takes care of serving the correct language automatically. This option is best suited when content is managed centrally, content is primarily (at least 75%) translated, and the website's organization is identical between the languages.
A use case where a single hierarchy makes sense is a white-labeled product such as an insurance policy. The number of pages and components needed to describe the policy is likely the same regardless of the visitor's language or location. Regional affiliate companies offering the same policy can enter content in their own language and serve it under their own brand.
This structure consists of separate website trees, one for each language. One site tree for English, another for German and so on. This effectively duplicates some pages but allows completely customized local content.
This option is best suited when less than 75% of total website content is multilingual. This option is also optimal when the content for each language is managed by separate teams or the site is organized differently for each language.
This structure is a mix where one tree is multilingual and others are monolingual. Use the multilingual tree for the international sections of the site. For each region or language, create a monolingual tree and merge it below the main tree. This option is best suited when the first level or two of your website is identical for all languages and countries.
How to choose
This decision tree helps choose a strategy.
Please be aware that the decision which strategy to choose has an impact on the way you define locales in a site, namely on the class that implements the I18n content support.