A content management system (CMS) or another content application implements a Clay Tablet Content Connector to:
- group multiple content items (assets) together, to send them to the translation provider as a single job or project. For details, see Grouping Assets for Translation and Grouping Assets into Jobs Using Job Metadata Interfaces.
- send files for translation to the Clay Tablet Platform storage buckets and translation request messages to the Clay Tablet Platform, using events. For a list and descriptions of these events, see Events a Content Connector Can Send. For an example of using events to send content for translation, see Code Sample: Sending Content for Translation .
- retrieve translated content from the Clay Tablet Platform, using events. For details, see Events a Content Connector Receives. For examples of using events to retrieve translated content, see Code Samples: Receiving Events.
The Clay Tablet Platform uses Message Queues to provide asynchronous communications with external applications, such as a CMS. For information about asynchronous communications, see http://en.wikipedia.org/wiki/Asynchronous_communication.
Note about the XML format of assets sent for translation: The format in which you send content for translation is important. There is an industry standard called XLIFF, which we recommend you review and adhere to if possible for content sent for translation. For information about this standard, see: http://docs.oasis-open.org/xliff/xliff-core/xliff-core.html