globalize translates the entries in a Contentful space and writes the translations back into the space's own locales. You link the space once and build a Workflow that watches it. From then on, publishing an entry starts the translation. Nothing is exported and no repository is involved.
Before you start
- Locales. Every language you want needs a locale in the Contentful environment (Settings, then Locales). The source language is always the environment's default locale.
- Localized fields. Each field you want translated needs Enable localization of this field switched on in the content model. Fields that aren't localized only hold the default locale, so there is nowhere to write a translation.
- Access. You need permission to install apps in the Contentful space.
Set it up
- In globalize, open Workflows, click New workflow, and under Input choose Contentful space.
- Click Install the Globalize App. Contentful opens in a new tab. Install the app in your space, then choose Connect to Globalize in the app's configuration and approve the connection.
- Back in the builder, pick the Space and the Watched environment. Each run reads from, and writes back to, the environment that name points to when the run starts.
- Under Content types, keep All content types, including ones added later, or narrow it to the ones you want.
- Check Target languages. They are filled in from the environment's locales.
- Under Translate automatically, choose what starts a run: When an entry is published, When a draft is edited, or both.
- Click Publish.
What gets translated
Plain text fields, Rich Text and Markdown. Other field types are left as they are.
Four ways to start a translation
| Trigger | What happens |
|---|---|
| An entry is published | The entry is translated and the translations are published with it |
| A draft is edited | A run starts 5 minutes after the last edit. Translations land as drafts, so you can read them before anyone publishes |
| Translate this entry in the Globalize sidebar | An editor translates one entry from inside Contentful and sees the status there |
| A manual run in globalize | Every entry the Workflow selects is translated |
Where the translations go
The Contentful write-back output writes each translation into the matching locale of the same entry, in the environment the run read. Entries that were published are published again with their translations. The run page lists delivery entry by entry.
Translations you already have
The first time a run sees a translation in Contentful that globalize didn't write, it adopts it. It isn't translated again and it costs no credit. If someone edits a translation in Contentful later, that edit is adopted too.
Quality
A new Workflow has two steps, Translate and QA. QA runs five checks and an AI review on every language before anything is written back. Style guides and context come from the Assets you attach to the Workflow.
If something looks wrong
- A language was translated but isn't in Contentful. The environment has no locale for it. The run translates it, keeps it in globalize and names it under delivery. Add the locale in Contentful and run again.
- The run fails with "no source text in the source locale". Check that the environment has at least one locale besides the default, and that the fields you expect are localized and filled in for the default locale.
- Your space isn't in the Space list. The Globalize App isn't installed in it yet, or Connect to Globalize wasn't completed in the app's configuration.
Contentful runs use the same translation credit as every other translation. See How is billing calculated?