All Collections
Connectors
Contentful
Configure the Contentful Connector in Locale
Configure the Contentful Connector in Locale
Joe Heider avatar
Written by Joe Heider
Updated over a week ago

Table of Contents

Introduction

Contentful is a leading content management platform that empowers businesses to create, manage, and deliver digital content across a variety of channels and devices. Known for its flexibility and scalability, Contentful enables organizations to streamline their content creation and delivery processes, supporting websites, mobile apps, and other digital experiences. When combined with Locale, you easily have access to an automated way of selecting content to be translated by your favorite MT engine, TMS system, or sent to your LSP of choice, all with just a few clicks.

What you’ll need to get started

  1. The Login link for Locale (https://app.locale.to/en/)

  2. The admin access credentials for your Contentful instance.

    1. Note: Locale does not have access to this information, nor do we provide this information. If you do not possess the correct credentials to access this information, please contact your system administrator or your Contentful representative.

  3. User login information for both your Locale instance, and your Contentful instance

    1. A trial account of Locale can also be taken for free by going to locale.to and selecting the “Get Started” button

Configuring the Contentful connector

  1. Start by accessing Locale with your username and password.

  2. Once logged into Locale (instructions on that can be found here) you’ll see a Dashboard which looks the image below.

  3. Select the Add Project button and you’ll be presented with the Locale Connector Store. Choose the CMS option in the menu filter to the left, and select the Create Project button under Contentful in the first row.

  4. Next will appear a unique Contentful key code which will be needed for the next steps. Select the small clipboard icon to copy this key, and select the Proceed to App Installation button.

  5. Next, choose the Contentful space and environment information that will be accessed by Lang Connector and the Locale platform which requires translation, and select Continue.

    1. In our case, we have a master space divided into a master and a staging environment, but some users may see a slightly different setup. So long as the correct spaces are selected here, the process will continue as normal.

  6. From the Manage Access Page comes the access authorization step. The dialog box will once again confirm the specific Contentful environment where translation content is needed.

    1. This is helpful to differentiate from a live production system from something like a testing or staging environment if this is something that exists within your organization.

  7. Selecting Authorize Access will finalize the authorization process between the Locale platform and our Contentful instance. Then we simply Go back to Locale to select the content for translation, and see our analysis information.

Creating a Locale project with the Contentful Connector

Once the steps above have been completed and you’ve added the necessary language pairs to your Contentful instance, you’re ready to create a project

  1. Locale will automatically detect the language pairs in the Contentful project and begin analyzing the content for translation in the Locale platform.

  2. Any content which has previously been translated, either fully or partially, will appear as such

  3. It’s also possible to select or deselect certain content pieces for translation by using the Content tab at the top of the screen

  4. Once all the necessary content has been selected for translation, it’s time to Push the content for translation. This can be done with AI, MT, or by choosing your preferred TMS of choice. In the below example, we’ll use a simple AI workflow.

  5. At this point, Locale will automatically send the content for translation, and when it’s complete, our status will update in Locale and our content will automatically be put back in our Contentful instance where it will be available for users to see.

Did this answer your question?