The key elements of this framework are:
Use one library per locale
A library should be created for the base site, and one library for each localized site, and another library for shared templates and components. When creating libraries, ensure that the correct locale is specified during the creation process, as this locale is used during search and in the multilingual user interface extensions.Same site structure in each locale
Note: If a language does not exist in the list of languages available when creating a library, you can add that language to the list of supported Web Content Manager languages.
For content to be recognized as being equivalent between sites, they must have the same URL path. This means the names and structure of all the site areas and content items in your site framework must be identical in each site if they are to be equivalent. The display titles can be different, but the names must match.Use workflow for all modifications
Creating, updating, publishing, expiring, deleting, and even moving content and components should be performed using workflow. This allows code to be triggered by the workflow to notify localized sites owners, automate parts of the localization process, and synchronize important stages in the workflow. Use shared templates and components
Workflows can be localized by creating an equivalently named workflow in each locale library. Localizing the workflow allows separate approval processes to be executed per locale and is also a requirement for regionalized sites. Localizing the workflow is part of synchronization process, and the provided extension for workflow synchronization has this ability.
Authoring templates, presentation templates, and components should be shared across locales as much as possible. Variability can be built in using workflows or workflow code that differs across locales, and presentation components that are picked up from the current locale.Parent topic: Using the multilingual solution
Presentation templates can be different across locales by having different mappings in each locale. While it should be avoided to ensure consistency across locales, major differences in layout or branding in some locales may necessitate this.
Authoring templates should be shared across localizes whenever possible with text providers used to provide localized template display titles, element names and help-text.