Brightspot CMS User Guide

Configuring site-level translation services


You can pre-configure combinations of settings for a translation service at the site level, making it easier for editors to send assets to the translation service without configuring every individual job. For example, you can pre-configure several Lingotek settings, and apply those settings to many translations. Editors can override the site-level settings for individual translations.

To configure site-level translation services:

  1. Click menu > Admin > Sites & Settings.
  2. In the Sites list, select the site for which you want to configure a translation service, or select Global to configure a translation service for all sites.
  3. Click search, located to the left of more_horiz, and type Translation.
  4. Scroll down to the Translation cluster, and from the Available Locales list, configure all the locales in which your site appears. (Brightspot uses this field to limit the target locales when submitting an asset for translation.)
  5. Configure groups of locales to which assets can be translated by doing the following:

    1. Under Locale Groups, click add_circle_outline.
    2. From the list, select Create New.
    3. In the content edit form, do the following:
      1. In the Name field, enter an identifying name for this locale group.
      2. From the Locales list, select the required locales.

        Locale group
        Locale group

      3. Click Save.
      4. Click Back. You return to the Edit Global or Edit Sites widget.
      5. From the Local Groups list, select the locale group you just configured.
  6. Configure service settings for the site by doing the following:
    1. Under Default Service Settings, click add_circle_outline.
    2. From the list, select Create New.
    3. In the Name field, enter a name for this service setting.
    4. In the remaining fields, configure the translation service as required. (There are different configurations for each translation service.)
    5. Click Save.
    6. Click Back.
    7. Repeat steps a–f to configure additional translation services.
    8. Click Save.
  7. Create content-type specific translation settings by doing the following:

    1. Under Type Settings, click add_circle_outline.
    2. Under Types, select the required content types.
    3. Under Completion Action, configure what Brightspot does with the returned translation.
      • Workflow—Brightspot assigns the translation to a workflow and state.
      • Draft—Brightspot saves the returned translation as a new draft.
      • PublishBrightspot immediately publishes the translation.
    4. From the Site Assignment list, select the site that owns the translation.

      • Source Content Site—Translation is owned by the site that owns the original asset.
      • Auto—Translation is owned by a group of sites associated with the translation's locale. For example, a group of three sites is associated with the locale es-MX. An asset is translated to that locale. The translation is associated with all three sites in the group.
      • Manual—Editors assign the site when initiating the translation.
      • User Site—Translation is owned by the site the editor was working on when initiating the translation. For example, John is working on the site Brightspot. Any translation he initiates is owned by the site Brightspot.
    5. Under Service Settings, select one or more translation services you created in step 6.
  8. Click Save.
Previous Topic
Integrating Lingotek with Brightspot
Next Topic
Sending an asset for translation
Was this topic helpful?
Thanks for your feedback.
The elements that get you up and running in a matter of days, from pre-built content types, to modules, to landing pages.

Content types
Modules
Landing pages
Everything you need to manage and administer content within Brightspot CMS, including plug-and-play integrations.

Dashboards
Publishing
Workflows
Admin configurations
A guide for installing, supporting and administering code on the Brightspot platform, including integrations requiring developer support to use.

Field types
Content modeling
Rich-text elements
Images