Date: Thu, 28 Mar 2024 12:14:35 +0000 (UTC) Message-ID: <1752697213.185.1711628075938@208e8dfb5a1e> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_184_1731539659.1711628075937" ------=_Part_184_1731539659.1711628075937 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Official website: https://www.contentful.co= m/
Supported content: entries (all generic fields).
The purpose of iLangL Contentful Connector is to provide localizat= ion flow between Contentful and a set of supported translation tools. =
iLangL Cloud is a middleware platform that is used to transfer con= tent between Contentful and translation tools, such as Memsource, memoQ Server, and SDL MultiTrans.
Workflow
Access the Content Management API secure= ly via HTTPS, and it will be available to iLangL Cloud authenticating with = a Contentful account (username and password). All interactions with Content= ful will be limited by account permissions. Password at iLangL side stored = encoded with hashing algorithm PBKDF2.
Read more about iLangL Security measures.&n= bsp;
The content elements extracted from Contentful Management API in J= SON format. The field values can be stored like plain text, HTML, JSON or m= arkdown. iLangL Cloud automatically processes JSON data and optimizes for t= ranslation tools. The original JSON format needs to be additionally process= ed to insert it back. The content processing tool makes sure that the trans= lated JSON file has the right processing for a successful import. iLangL sy= stem can process URLs and automatically remap language codes from master to= target language.
Before starting the localization, the iLangL team can help to buil= d 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 hav= e one parent item that represents the page and refers to other content elem= ents, 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 p= arent item and all child items in one translation package. iLangL channel c= onfiguration 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 wi= ll be translated.