Support and Documentation

Translation

With the Translation plugin, you can submit content to an online translation service directly from Brightspot, and then review the translation before final publication.

Overview of Translations

Brightspot integrates with online translation services such as Lingotek.

translation-workflow.svg

Referring to the previous illustration, you need two components to submit an asset for translation:

  • An asset—An article, blog post, or any other asset you create in Brightspot.

  • Job settings—The online translation's configuration used to ingest the asset and perform the translation, the locale in which to translate the asset, and the workflow within Brightspot after receiving the completed translation.

The following sections describe how to configure Brightspot to use an online translation service, and how to submit an asset for translation.

Integrating translation services

Integrating Lingotek with Brightspot
Integrating Amazon Translate with Brightspot

Administrators perform this task.

Procedure. To integrate Amazon Translate with Brightspot:
  1. Obtain the following from your AWS console:

    • The input bucket (Brightspot pushes files to be translated to this bucket.)

    • The output bucket (Brightspot retrieves completed translations from this bucket.)

    • Translation role ARN (This role has access to the input/output buckets as well as the AWS Translate service.)

    • AWS region

  2. From the Navigation Menu, select Sites & Settings.

  3. In the Sites widget, select Global. The Edit Global widget appears.

  4. Under Main, expand AWS Translation.

  5. In the Input Bucket, Output Bucket, Translation Role ARN, and AWS Region fields, enter the values you obtained in step 1.

  6. In the Task Host field, enter the Brightspot task that monitors translation progress.

  7. Click Save.

  8. Continue with the following steps:

Configuring site-level translation services

Administrators perform this task.

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.

Procedure. To configure site-level translation services:
  1. From the Navigation Menu, select Sites & Settings.

  2. In the Sites & Settings 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. In the Edit Site or Edit Global widget, under Main, expand Translation.

    translation-accordion.png
  4. 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. Create a service for the site by doing the following:

    1. Under Default Service Settings, click |mi-add_circle_outline|. A selection field appears.

    2. Click |mi-search|. A content picker appears.

    3. Under Create, click New Lingotek. (If you use a different translation service, contact your Brightspot representative to add it.) A content edit form appears.

      new-lingotek.png
    4. In the Name field, enter a name for this translation service.

    5. In the remaining fields, select the project, workflow, filter, and vault as required.

    6. Click Save.

    7. Click Back to Add to Default Service Settings. You return to the content picker.

    8. Select the translation service you just created, and close the content picker. You return to the Edit Site or Edit Global widget with the selected translation service in the Default Service Settings list.

    9. Repeat steps a–h to configure additional translation services.

    10. Click Save.

  6. Under Type Settings, do the following:

    1. Click |mi-add_circle_outline|. A form appears.

      translation-type-settings.png
    2. Under Types, select the content types you will be sending for translation.

    3. Optional. Under Completion Action, configure what Brightspot does with the returned translation.

      • If you select Workflow, select the workflow to which Brightspot sends the returned translation.

      • If you select Draft, Brightspot saves the returned translation as a new asset with a status Draft.

    4. Under Service Settings, select one or more translation services you created in step 5.

  7. Click Save.

Sending an asset for translation

Editors perform this task.

Procedure. To send an asset for translation:
  1. Create the asset you want to send to translation. Click Publish or the appropriate button for your workflow.

  2. In the editorial toolbar, select |mi-more_horiz| > Translate This Article. Step 1 of an Options wizard appears.

    translation-options.png
  3. From the Service list, select one of the following:

    • One of the translation services that your administrator already configured for you.

    • Manual to translate content manually within Brightspot. Use this option to create localized content without using an external service.

  4. From Referenced Content, select any additional fields you want to translate. The available fields are those for which you defined a site-level translation service as described in Configuring site-level translation services.

  5. Click Next. The next step in the wizard appears.

    translation-target-locales.png
  6. In the Target Locales field, select the locales to which the asset is translated.

  7. Click Translate.

Brightspot displays a confirmation message, and lists the translation assignment under |mi-more_horiz| > Translations. You can also view the submission in Lingotek.

translations-tab.png