Add a language

To address the demands of global markets, you can globalize and localize Sitecore Content Hub™ by adding languages. Standard language codes (for example, en-US, nl-BE, and so on) are included as a template that you can extend and customize.

To add a language:

  1. Add a portal language
  2. Add language translation manually, or Export language translation as a template

Add a portal language

To add a portal language:

  1. On the menu bar, click Manage .

  2. On the Manage page, click Portal languages.

  3. On the Portal languages page, click + Portal language.

  4. In the Portal language dialog box, in the Name field, enter a name for the new language.

  5. From the Culture list, select a culture.

    The culture is the same as the standardized language code. Type in the search box to narrow down the list of available cultures.

  6. Optionally, in the Label field, add a label.

  7. Click Save.

Add language translation manually


To minimize mistakes when adding translations, we recommend using the export feature to export the newly created language to Excel and update values in a spreadsheet. You can then import the new values back into Content Hub.

On the Translations page, the new language shows in the drop-down list. The culture displays as the standardized language code (for example, the English (Ireland) culture corresponds to the language code en-IE). Hover over the language code to see the full name of the culture.

Even though you created the portal language, there are no values created by default. As a superuser, you must add the new language values.

To add language translations:

  1. On the menu bar, click Manage .

  2. On the Manage page, click Translations.

  3. Next to the entity for which you want to define translations, click View detail page .

  4. In the right-corner of the application window, from the drop-down list, select the language you want to add values for.

  5. Click Edit .

  6. In the Template field, enter the translated value and click Save.

    You can see the new value on the Translation page. In the following example, we added a french label to the addAllToSelection component.

Export language translation as a template

To export the language translation as a template:

  1. On the menu bar, click Manage .

  2. On the Manage page, click Translations.

  3. Click Export.

  4. In the Export translations dialog box, select the checkboxes next to the translations you want to export and click Export.

    The export package is available in Downloads and shows initially with a Processing status. You can access downloads from the Profile icon in the top-right corner of the application window. When the export package is complete, the status becomes Ready.

  5. Click Download icon .

  6. Go to the location where you saved the Excel file and open the file. The Excel file contains eight worksheets:

    • Portal.Translation

    • Definitions

    • Datasources

    • Portal.Page

    • Portal.PageComponent

    • M.Project.TaskType

    • M.Project.BlockType

    • Portal.Component

      On the Portal.Translation worksheet, there is a column with the header that contains Values# that has the standardized language code of the new language appended.

  7. Insert the TranslationName values for the translation.

  8. To see the original values of TranslationName, export the default en-US translation language. In this export, you can see the OriginalValue#en-US values.


The other worksheets already have values inserted by default. You can modify these as required. Templates include standard fields only. Customization of your schema or taxonomy does not affect the contents of the downloaded template. Because some worksheets (such as Sandbox, M.PCM.ProductFamily, and M.Brand) are sample data, they have no values when downloaded.


The Definitions worksheet contains the translations for the Helptext value for each definition label.


The Datasources worksheet contains the translations for:

  • Statuses

  • States

  • Permissions

  • Action types

  • Job types

  • Durations


The Portal.Page worksheet contains the translations for the page names (for example, Manage page, Assets page, Projects page, and so on).


The Portal.PageComponent worksheet contains the translations for components contained in the portal pages (for example, the title of the page, back button, navigation button).


The M.Project.TaskType worksheet contains translations for project tasks (for example, annotate, download, like, upload files, upload versions).


The M.Project.BlockType worksheet contains the translations for the project block types.


The Portal.Component worksheet contains translations for page components.


On the Portal.Translations worksheet, we recommend that you delete the TranslationName column to avoid an error during the import. This column does not allow updates. The import may still be successful even if the column is not removed.

Import the translation

To import the translation:

  1. On the menu bar, click Manage .

  2. On the Manage page, click Translations.

  3. After you have updated the Excel spreadsheet as required, on the Translations page, click Import.

  4. In the Upload file dialog box, click Select file and go to the completed translation Excel spreadsheet and click Open.

  5. To see the progress of the import job, on the menu bar, click the profile icon and select Background processes.

    On the Background processes page, the job status is displayed in the Condition column.

    A message displays once the import is complete.

The new language or translation is now available for use. Log in directly to the translated environment by adding the standardized language code to the address of the instance, for example, https://stylelabs.io/en-IE.

Set the default language

To set the default language:

  1. In the upper-right corner of the application window, click the profile icon and select Profile.
  2. On the profile page, click More actions and select Change language.
  3. In the Change language dialog box, select the language you want to display by default.
  4. Click Save.

Can we improve this article ? Provide feedback