Integrations

Kontent by Kentico

Available for

  • Enterprise edition

Get in touch with Sales for licensing questions.

Kontent by Kentico is a headless CMS providing the infrastructure to create and manage content. It is not coupled to any single presentation layer allowing the distribution of content to any platform or device.

All translatable fields are imported for localization unless flagged as non-localizable in Kontent.

Translatable content elements:

  • text

  • rich text

  • assets

  • linked items

Translatable media assets are also supported. To access assets, select Assets as the Default folder when setting up the connector or as a folder to be monitored in APC. Target files are uploaded to locations defined in APC or CJ.

Use Cases

There are a number of use cases for the connector:

  • Project Managers can add files directly to projects from an online repository.

  • Set up the submitter portal to allow Submitters to add files to requests directly from the online repository.

  • Use Automated Project Creation (APC) to have Memsource automatically create new projects when a change in the specified workflow states is detected.

    • Selected content items are imported the very first time APC runs.

  • The Connector API can be used to automate steps otherwise performed manually through the UI. Webhooks can be used to have Memsource notify 3rd party systems about certain events (for example, a job status change).

Kontent Settings

  1. Log in to your Kontent account and open the selected project.

    The Home page opens.

  2. Navigate to Project Settings and click API Keys.

  3. Copy the Delivery API Key (Project ID).

    This key is required for the connector configuration. This connector will only be able to browse and monitor this Kontent Project. If another Project needs to be monitored, create a new connector with a new Delivery API key (Project ID) for that project.

  4. Copy the Management API Key.

    This key is required for the connector configuration. This key allows access to unpublished content items to be localized before publication.

Memsource Settings

  1. From the Settings Setup_gear.png page, scroll down to the Integrations section.

  2. Click on Connectors.

    The Connectors page opens.

  3. Click New.

    The Create Connector page opens.

  4. Provide a name for the connection and change the Type to Kentico Kontent.

  5. Select how the connector should import linked content items.

    Remote Kontent workflow steps are respected for linked items. If the selected content item is set to Translate, yet all linked items are in Draft they will not be imported. Selected items and their linked items both require the initial Translate workflow step to be imported by APC. This is ensure that only content that is explicitly intended to be localized by the content author is imported.

    • Selected content item only

      • Content that is explicitly selected when adding from the repository is imported.

      • Changes detected by APC are imported for translation.

    • Include linked content items

      • The connector traverses the entire hierarchy of linked content and imports all translatable fields for translation.

  6. Enter Project ID (Delivery API Key) obtained from the Kontent site.

  7. Enter Management API Key obtained from the Kontent site.

  8. Provide Translate to languages specified in (APC).

    Automated Project Creation will only create jobs for languages specified by codes in the given field that is specified by a unique ID (e.g. target_languages). Codes can be followed by language names as long as they are separated by a comma (e.g. de-DE German (Germany)).

    Language codes are case insensitive and can use either _ or formatting - (e.g. de_de, de-de, de-DE).

    Note

    To select target languages on the content item level, create a new Taxonomy Group (Content Model > Taxonomies) within the selected Kontent Project ID. The newly created group (e.g. Target Languages) should contain the language codes of all localization languages configured in the selected project. Add the configured taxonomy group to all or selected content models as a supporting element. Once added, the codename can be obtained.

  9. Select Source language.

    This setting does not impact the default language in the project. The source language for the connector itself is language agnostic and any localization languages that are configured for a particular project can be used as the source language for the connector.

    If using Kontent with multiple source languages, set up multiple instances of the connector with different source languages configured in this field.

  10. Click Test connection.

    A checkmark will appear if the connection was successful. A red exclamation point will appear if it wasn't. Mouse over the icon to see additional details.

  11. Select Kontent workflows.

    By configuring workflows for a Kontent Project, the workflow can be tuned to provide localization when needed. Kontent workflows are configured for each project individually. By setting the Delivery API Key (Project ID) in the connector configuration, only the remote workflow steps for the specified project ID are displayed.

    • Translate articles from:

      The connector monitors articles in the selected stage (e.g. Translate). The author can apply this label to articles when ready for translation.

    Upon import from Kontent:

    • Set source articles to

      The connector advances the workflow to the selected stage (e.g. Translation in Progress) when the source articles are downloaded.

    Upon export to Kontent:

    • Set source articles to

      The connector sets the workflow stage of the source articles to the selected stage (e.g. Translations Completed) when the translation is exported.

    • Set translated articles to

      The connector sets the workflow step of the article translations to the selected stage (e.g. Translation ready for Review) when the translation is exported.

  12. Click Save.

    The connector is added to the list on the Connectors page.

Was this article helpful?

Sorry about that! In what way was it not helpful?

The article didn’t address my problem.
I couldn’t understand the article.
The feature doesn’t do what I need.
Other reason.

Note that feedback is provided anonymously so we aren't able to reply to questions.
If you'd like to ask a question, submit a request to our Support team.
Thank you for your feedback.