Content engine

An engine is an extension of the Lokalise API that encapsulates most heavy-lifting required for building apps. For example, the engine can deal with standardized flows, simplify the interactions with the Lokalise API, and run tasks that process content and synchronize it between different systems. Therefore, implementing apps using an engine is easier, faster and less error-prone, as you can leverage all the pre-built functionality.

The content engine facilitates the content exchange between Lokalise and other content management systems. The content engine does the following:

• It initiates the authorization with content platforms, and handles the project configuration.
• It manages the mapping of content items with Lokalise keys, and takes care of obtaining the latest known state.
• It takes care of the credential storage, so that connectors can be stateless (no database required).
• The Lokalise UI that allows users to manage content exchange relies on the engine.

In order to connect to third parties, the content engine allows any developer to build their own connector using the hosted app architecture: the hosted connector will act as a bridge between the content platform and Lokalise content engine, and will enable users to connect both systems, select the content they want to translate, transfer it to Lokalise, see the translation status, and receive the translated content back. Read more about the technical implementation requirements.

Custom processor

The custom processors enable developers to implement their own middleware server, and implement custom workflows and integrations into the process of importing and exporting translation content.

By creating a custom processing server, and connecting it to Lokalise, developers can manipulate data, connect to 3rd-party services, and introduce their own custom logic into the processes.

Read more about the custom processor, and how to implement it.