This feature is available in the Business plan

Key clustering in Localazy provides a unique solution for handling duplicate values without modifying the integration source. By utilizing key clusters, you can save time and resources by eliminating the need to translate the same content multiple times.

How it works #️⃣

When key clustering is enabled, content uploaded from API-based sources is automatically processed and organized into key clusters if the uploaded value already exists in the target file. It’s important to note that key clusters are specific to a file. If you upload a duplicate value to a different file, the keys won’t be clustered since their origin is different.

API-based sources include the Localazy API integration itself and all supported plugins and extensions such as Figma, Strapi, and Storyblok.

Enable key clustering #️⃣

To enable key clustering, navigate to the project’s general settings section and enable the Key clustering option under the Import & Export settings. Article Image

Once enabled, when you upload content through API-based integration with duplicate values, you will find a special cluster type of key labeled with cluster_ and nested keys from the source. Article Image

Split a cluster #️⃣

If the uploaded key’s value remains the same, but the meanings differ, it is recommended to split the cluster into two separate clusters. This allows each cluster to be translated according to its specific meaning.

For instance, let’s consider the word Type, which can have two different meanings: to write something or to specify a kind of something. To split the cluster, navigate to the detail page of the source key and locate the split cluster button. Clicking on this button will prompt you to specify the suffix, included keys, and optionally add a translation note. Additionally, you can decide whether the new cluster should become the new default cluster. All future uploaded keys with the same duplicate value will be nested under the default cluster. Article Image

Key Clustering vs. Duplicity Linking #️⃣

Key clustering and Duplicity linking share the common goal of reducing duplicates in your project, but they have some key differences:

  1. Automatic vs. Manual Management: Key clustering works automatically for content uploaded from API-based sources, while duplicity linking requires manual management from the Localazy interface and can be used for any content.
  2. File Scope vs. Cross-File/Project Scope: Key clustering operates within a file, while duplicity linking can be applied across multiple files and even multiple projects.
  3. Source Key Count: Additional keys within a cluster do not count toward the source key limit. With duplicity linking, each linked key counts towards the source key limit. There is no limit or additional cost based on the number of links.
  4. Handling Homonyms: Key clustering automatically clusters keys with identical values, even if they have different meanings (e.g., homonyms like “book,” “type,” or “left”). In contrast, duplicity linking requires manual linking of true duplicates, but automatic linking of homonyms does not happen.

In general, key clustering is most beneficial when you upload content through API-based integrations and prefer to manually handle homonyms rather than linking true duplicates manually.

This feature provides significant time and cost savings, particularly when integrating with CMS platforms like Strapi and Storyblok, as well as utilizing the Figma plugin. This is especially beneficial if you choose to use Figma as the Source of Truth for your localization process.

Terminology #️⃣

Key cluster #️⃣

A Localazy key in which keys with duplicate values and upload from API-based sources are nested.

Split cluster #️⃣

A process to split a single Localazy cluster key into two in cases where the nested keys hold different meanings and have to be translated differently.

Default cluster #️⃣

When there are multiple clusters with the same value (the original one has been split), the default cluster will be selected as the target for nesting of all future uploaded keys with the duplicate value.