Content Delivery

Distribution is a CDN vault that mirrors your project’s translated content and is required for integration with the iOS, Android, or Web apps.

Distribution Setup

To configure a distribution, follow these steps:

  1. Open your project and go to Tools > Content Delivery. Over-the-Air Content Delivery
  2. Add new distribution using the Add Distribution button.
  3. In the appeared dialog, name your distribution.
  4. Select only the files, translations for which you want to be shown in your application.
  5. Select one of the following export options:
    • Default export – export translations in the original format of the selected files.
    • Target file bundles – export translations in the selected format regardless of the original format of the selected files. Read more about configuring target file bundles for distribution.
  6. Click Create.
    Over-the-Air Content Delivery
  7. Copy the distribution hash so you can use it for integration.
    Over-the-Air Content Delivery
  8. Сreate as many distributions as you need and select different files for each. You’ll need to click Release next to the needed distribution every time you want to send new translations to the app.
    Over-the-Air Content Delivery
Note: CDN caches all the translations in release for up to 1 hour, and even when new translations are released in Crowdin Enterprise, CDN may return them with a delay.

For Mobile Applications

To send the translated content to your mobile apps via content delivery, use the Crowdin SDKs:

For Web Applications

To send the translated content to your web apps via content delivery, use the Crowdin OTA JavaScript client.

Read more about Crowdin OTA JavaScript client.

To manage the translated content delivery to your web apps manually, use the following instructions:

Form the URL to the translation file the following way:{distribution_hash}/content/{path_to_file}

{path_to_file} will be the same as for the regular translation build. If your files don’t have export patterns with the language code placeholders (e.g., %locale%, %two_letters_code%, etc.), the system will automatically add the Crowdin language code at the beginning of the path.

You can find the list of your project language codes in the meta-information about your distribution content:{distribution_hash}/manifest.json

War dieser Artikel hilfreich?