This use case describes how to select 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.

Single tree

Magnolia can store multi-language content in a single JCR content node. This means you only need a single site hierarchy. A single tree stores each translation as a property under the same parent content 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.

Multiple trees

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 organization of the website for each language differs.

Mixed trees

This structure consists of a mix of trees where one tree is multilingual and others are monolingual. Use the multilingual tree for the main 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.

See also

#trackbackRdf ($trackbackUtils.getContentIdentifier($page) $page.title $trackbackUtils.getPingUrl($page))
  • No labels