Manage Content Translation in Contentstack

Contentstack does not offer translation services but we provide the ability to integrate with third-party translation providers and translate content. Using Contentstack workflows, set up a webhook to trigger when your workflow stage changes to “Send to Translation”. Once the webhook triggers, initiate the translation process. You can use any popular translation tool, such as Worldserver and iLangl, to translate content.

Below is a detailed guide on how some of our customers have achieved this. Please note, each customer’s process may vary and this guide is meant to be a point of reference to help you get started.

Manage Content Translation in Contentstack.jpg

Let’s have a look at the steps involved throughout the process of translating content.

Step 1 – Setting up the essentials

First, create your stack, and add content types, entries, at least one additional language, and a publishing environment.

Once you have your initial stack configured, then you’re ready to begin the integration process for translation.

Step 2 – Set up workflows for translation

To set up workflows for the translation process within Contentstack, follow the below steps:

  1. Create a workflow by navigating to the settings icon > Workflows > Add Workflow.
  2. Create your workflow stages and transition rules to fit your content editorial team’s process.

Sample translation process

Below is an advanced workflow example for translation. Please note, this can be simplified or modified to fit your team's process.

  1. Copy and assets are approved and do not change after translation is requested.
  2. Copy and assets change during translation.
  3. Found an error on the live site and translation needs to be amended.
  4. Found an error on live site and English and translation need to be amended.
  5. Found an error on live site and only English needs to be amended.

The diagrams below show the different workflow stages set up for a sample translation process:

1_Copy and assets are approved ands do not change after translation is requested.jpg

2_copy assets change during translation.jpg

3_Found Error on live site and translation needs to be amended.jpg

4_Found Error on Live site and English AND translation needs to be amended.jpg

5_Found Error on Live site and Only English needs to be amended copy.jpg

Step 3 – Trigger a webhook to initiate translation

Contentstack outputs JSON content via its powerful APIs. A simple way to get content out of Contentstack into a translation tool such as iLangl and Worldserver is to utilize our webhooks. You can think of webhooks as a trigger event for anything that happens in Contentstack. Webhooks also send the entire JSON payload when called for easy integration.

Let’s have a look at the steps involved in creating a webhook to send content for translation.

  1. Create a webhook by navigating to the settings icon > Webhooks > + New Webhook.
  2. Under the ‘When’ section, select the options Any > Entry > All > Workflow Stage Changed > (Workflow name) > (Stage name ex. “Send to Translation”).
  3. image2.png

    This will configure your webhook to trigger on a workflow stage change such as “Send to Translation”, like in the above workflow example.

    Step 4 – Translate content using a translation provider

    The translation provider can now retrieve your JSON output upon receiving the webhook call on a secure translation server. Most providers will map the JSON output to strings using our UID fields as keys, then provide the translated output and send it back to Contentstack via the Content Management API. Most providers also provide what’s called “Translation Memory” and store already translated values for quicker turnaround times for localization.

    To translate content, work with your translation provider to configure the mapping of JSON strings and keys for translation.

    Here is a video from one of our partners, iLangL.

    Step 5 – Use Content Management APIs to update translated content

    Contentstack offers powerful Content Management API calls which allow you to perform almost everything you can do in our web UI, such as updating entries and changing workflow stages.

    Let’s have a look at the steps involved in updating translated content with the use of these APIs:

    1. Work with your translation provider to configure the update entry API, which will use the language parameter to pass the translated strings back into the entry.
    2. After the strings are passed into the entry, update the workflow stage to ‘Review Translation’ or similar via our Content Management API.

    This would take place if your translation provider were to supply this type of output and your market specific experts go in and review the machine translation.

    The following translation integration diagram lists the steps and decisions needed to perform the translation process with Contentstack:

    image4.jpg

Was this article helpful?
top-arrow