To give you the flexibility to support your particular workflow, Dynamic Content supports two methods of localizing your content: field level and content item level localization.
Both methods of localization use locales, an ISO standard combination of languages and country codes. With field level localization, users create a single content item with fields for each supported locale, while content item localization allows you to create a separate content item for each locale.
On this page we'll provide you with an overview of each type of localization and include links to pages that explain each method in more detail.
Field level localization
To support field level localization, developers need to create content types containing properties that are localizable so that users can enter separate values for each locale in each localizable field.
See the Creating localizable content types for more details on creating localizable content types.
For users, creating localized content is the same as creating any other type of content and additional features allow you to visualize content for each locale and filter by locale to focus on the particular languages you are working on.
More details about working with localized content when using field level localization is on the Creating and editing localized content page.
Field level localization is a good choice if:
- You have a single site and support a small number of locales
- You have an inhouse team that handles your localization
- You don't have a requirement to schedule and publish content for different locales at different times
Content item localization
With content item localization, when you choose to localize a content item new variants of the item will be created for each locale you selected. These variants will be separate content items, each with their own unique ID and revision history.
Localizing content is shown in more detail on the Content item localization page.
When content is localized, the locale is displayed on its card. The image below shows fr-FR and de-DE variants of the "Winter collection image".
Localized content can be created either in the same repository or in a repository to which one or more locales have been assigned. This allows you to set up repositories to contain content localized for particular locales, and makes it easier to share translation work among different teams.
You can also localize content such as carousels or grids, that contain other content items. The Localizing linked content page shows the different scenarios for localizing content that contains links to other content items.
Content item localization is a good choice if:
- You have many sites and support many locales across those sites. Typically each site would also have its own set of slots
- You use several teams for localizing content into particular locales or groups of locales
- You use external localization providers and want to restrict write access to only those repositories that each team is working in
- You want to have the option to schedule and publish different locales at different times
Locales are associated with a Dynamic Content hub. A locale is a combination of language code and country code, with the language code being mandatory and the country code optional.
To manage locales, choose the "Locale settings" menu item as shown in the image below.
From the Locale settings window you can add, edit and delete locales, with the exception of the master locale. The first locale added will be the master locale and once this is set it cannot be changed. The master locale will be used by default for cards and visualizations in the content library.
To add a locale click the "+" icon at the bottom of the list of locales and choose the language code and, optionally, the country code.
For example, you might wish to provide a localized string for Portuguese, in which case you would add one locale with just the pr language code, or there may be a requirement to localize separate strings in Portuguese for Portugal (a locale code of pt-PT) and Brazil (pt-BR).