Plan a second language #

A German version of a site with its own menu and, where needed, its own layouts.

Life cycle: Plan, example 10 of 35. Worked out on the Fit & Healthy site of Exponential 6.0.15+.

Contents #

1. In the Layouts editor
2. With settings and templates
3. Which to choose
4. Check

In the Layouts editor #

1. A mapping can have a Siteaccess condition (a list: site, admin, classic, bold, bold_ger ...). The Starter mappings use siteaccess: starter, starter_ger.
2. Plan which page types need a layout per language and which share one.

With settings and templates #

1. Each siteaccess has its own menu.ini (exp:ini where menu.ini/SiteInfo/MainMenuID <siteaccess>), so the header menu can differ.
2. Translatable template texts use |i18n( 'context' ) and the translation files of your extension.

Which to choose #

Share layouts across languages unless the composition really differs; the content is translated anyway.

Check #

• The plan lists the siteaccess of each language.

Related pages #

• Which layout does a page get?
• Plan examples, every page
• Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.