Document Type Localization

The Umbraco backoffice is localized to match the user's configured language.

When defining a Document Type, you can apply localization to:

• Document Type name and description.

• Property names and descriptions.

• Custom property validation messages.

• Tab and group names.

Setting up localization for Document Types is a two-step process:

• Create the localizations in user defined backoffice localization file.

• Apply the localizations to the Document Type.

Creating localizations

Once you have registered a backoffice localization file, you can add your localization texts for use in Document Types. The following localizations are used for the samples in this article:

export default {
    contentTypes: {
        article: 'Article page',
        'article-desc': 'A textual, article-like page on the site. Use this as the main type of content.',
        landing: 'Landing page',
        'landing-desc': 'An inviting, very graphical page. Use this as an entry point for a campaign, and supplement with Articles.'
    },
    tabs: {
        content: 'Page content',
        seo: 'SEO configuration',
    },
    groups: {
        titles: 'Page titles'
    },
    properties: {
        title: 'Main title',
        'title-desc': 'This is the main title of the page.',
        'title-message': 'The main title is required for this page.',
        subTitle: 'Sub title',
        'subTitle-desc': 'This is the sub title of the page.',
    }
};

Applying localizations

The localizations are applied by using the syntax #{area alias}_{key alias}.

1. Create a Document Type with template called #contentTypes_article with alias: articlePage.

2. Under the newly created Document Type follow these steps:

• Name the description to #contentTypes_article-desc.

• Create a new tab called #tabs_content.

• Add a new group called #groups_titles.

• Add a property called #properties_title with alias title.

  • Set description to {#properties_title-desc}.

  • Use a TextString editor.

  • Enable to Set this field as mandatory.

  • Under validation add #properties_title-message.

• Add a property called #properties_subTitle with alias subTitle.

  • Set description to {#properties_subTitle-desc}.

  • Use a TextString editor.

• Enable Allow at root in the Structure tab.

1. When creating and editing the content, you will see that the backoffice now uses the configured localizations.

1. Create a new "Article" content:

1. When trying to save the content without adding the mandatory content, you will see a warning as expected: