Configuring translation


Brightspot offers a number of options to translate your content. These options fall under two categories:

  • Manual translation—Refers to translation performed manually by a human being in the CMS.
  • Translation services—Refers to translation performed via integrations with translation service providers.

There are several configurations that are common to manual translation and translation services, such as what locales are available, and how the content is saved when translated. This topic explains these settings. However, integrated translation services may require preliminary configuration to enable before proceeding with the configurations explained in this topic.

Note
If you are configuring manual translation, follow the steps listed in this topic.

If you are configuring translation services, do the following:
  1. Refer to the topics below depending on the translation service with which you are integrating:
  2. Return to this topic and follow the steps listed below.


To configure translation services:

  1. Click menu > Admin > Sites & Settings.
  2. In the Sites widget, click the site for which you want to configure a translation service, or click Global to configure a translation service for all sites.
  3. Under CMS, expand Translation.
  4. Configure the following fields (that apply to all content types) by doing the following:
    1. From the Available Locales list, select the locales to which editors can translate content. (Brightspot uses this field to limit the target locales when submitting an asset for translation.)
    2. (Optional) From the Locale Groups field, create groups of specific locales that editors may select to more quickly translate for their desired audiences. For example, if you cater to a large variety of locales, but the majority of your translation efforts are for Spanish (Mexico) and German (Austria), you can set a locale group for those two locales and speed up an editor's workflow when sending assets for translation.
      Note
      Depending on your Brightspot implementation, you may see a Default Service Settings field below Locale Groups. This field is only used when integrating with Lingotek. For details, see Integrating Lingotek with Brightspot.
  5. Configure the following fields (that apply only to specific content types of your choosing) by doing the following:
    1. Under Type Settings, do the following:
      1. Click add_circle_outline Add Type Setting.
      2. Under Types, select the content types editors can send for translation.
      3. Under Completion Action, configure what Brightspot does with the returned translation.
        • Publish—Publishes the translated asset.
        • Draft—Saves the translated asset as a draft.
        • Workflow—Submits the translated draft into a workflow. In the Workflow Return State, select the workflow state to which the translated asset is submitted.

        After selecting one of the options above, select one of the following options for the Site Assignment field.

        • Source Content Site—The translated asset is owned by the same site from which it was sent for translation.
        • Auto—The translated asset is owned by a site that is automatically set based on available locales on configured sites.
          • Sites—Select Shared or One-Off.
            • Shared—The translated asset is owned bya group of sites that you configure in the Site Group field.
            • One-Off—The translated asset is owned by individual sites that you designate in the Sites field.
        • Manual—The translated asset is owned by the designated site.
        • User Site—The translated asset is owned by the same site that the editor was in when the asset was submitted.
  6. Click Save.
Note
When finished, you can send assets for translation from the asset's content edit form. For details on this process, see Sending an asset for translation.

Our robust, flexible Design System provides hundreds of pre-built components you can use to build the presentation layer of your dreams.

Asset types
Module types
Page types
Brightspot is packaged with content types that get you up and running in a matter of days, including assets, modules and landing pages.

Content types
Modules
Landing pages
Everything you need to know when creating, managing, and administering content within Brightspot CMS.

Dashboards
Publishing
Workflows
Admin configurations
A guide for installing, supporting, extending, modifying and administering code on the Brightspot platform.

Field types
Content modeling
Rich-text elements
Images
A guide to configuring Brightspot's library of integrations, including pre-built options and developer-configured extensions.

Google Analytics
Shopify
Apple News