Supported content: entries (all generic fields);.
The purpose of iLangL Contentful Connector is to provide localization flow between Contentful and a set of supported translation tools.
How does it work?
- iLangL Cloud system connects to Contentful CMS via web API. Contentful Content Management API is used for localization flow between Contentful and translation tools. Content Management API: https://www.contentful.com/developers/docs/references/content-management-api/. Read more about iLangL Connection requirements.
- Extracts the content for translation and processes it hiding all the sensitive data from the translation tool.
- The jobs in memoQ are created automatically and their progress can be tracked in iLangL Cloud.
- When the translation is finished, the translated files are sent to Contentful and the drafts of pages for certain language versions are created automatically.
Access the Content Management API securely via HTTPS, and it will be available to iLangL Cloud authenticating with a Contentful account (username and password). All interactions with Contentful will be limited by account permissions. Password at iLangL side stored encoded with hashing algorithm PBKDF2.
Read more about iLangL Security measures.
The content elements extracted from Contentful Management API in JSON format. The field values can be stored like plain text, HTML, JSON or markdown. iLangL Cloud automatically processes JSON data and optimizes for translation tools. The original JSON format needs to be additionally processed to insert it back. The content processing tool makes sure that the translated JSON file has the right processing for a successful import. iLangL system can process URLs and automatically remap language codes from master to target language.
Before starting the localization, the iLangL team can help to build translation scope and identify which content types need to be included in localization.
Contentful provides flexibility to build different page types and more than one content type can be used to build an HTML page. In this case, many content elements can represent different HTML pieces. Usually, we have one parent item that represents the page and refers to other content elements, such as carousel, header, footer, etc. In case you want to export all items in the scope of the one page, it might be hard for you to select a parent item and all child items in one translation package. iLangL channel configuration allows defining parent/child structure between content types, and when you pick the parent content element, all referenced items will be exported in the same translation batch automatically. This helps to make a translation order easy and improve the quality of translation by providing the entire page context for a linguist and ensuring that all page blocks will be translated.