docs(figma): document translating Figma variables and refresh the plugin article - #887
docs(figma): document translating Figma variables and refresh the plugin article#887andrii-bodnar wants to merge 1 commit into
Conversation
…gin article Update both the Crowdin and Crowdin Enterprise articles: - Add a "Translating Figma Variables" section covering supported collections, sending default-mode values to Crowdin, syncing translations into per-language modes, screenshots, and the Figma plan mode limit - Note that Sync Translations stays disabled until the selected collections have variables linked to Crowdin strings - Note that text layers bound to a variable are read-only in the string list and unaffected by in-place preview - Move the key naming pattern instructions from the Settings tab to the String Defaults dialog, and document the camelCase style and custom pattern placeholders - Describe how duplicated linked elements are treated and the warning shown before updating linked strings - Replace the stale Submit button label with Send to Crowdin in the add-strings flows - Mention that the Variables tab is unavailable in Dev Mode Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
| 1. Open the Crowdin plugin for Figma. | ||
| 2. Switch to the **Variables** tab. | ||
| 3. Select the variable collections you want to translate and click **Send to Crowdin**. | ||
| 4. Review the list of strings to be added. String keys are generated from the collection, group, and variable names. You can edit each string's key and context individually or configure the key naming pattern for all of them by clicking <Icon name="mdi:cog-outline" class="inline-icon" /> above the list. |
There was a problem hiding this comment.
The gear panel here also has Max. Length Correction (%) and the camelCase option, not just the key naming pattern. It's the same String Defaults panel as in the Strings tab, worth saying so
| 2. Switch to the **Variables** tab. | ||
| 3. Select the variable collections you want to translate and click **Send to Crowdin**. | ||
| 4. Review the list of strings to be added. String keys are generated from the collection, group, and variable names. You can edit each string's key and context individually or configure the key naming pattern for all of them by clicking <Icon name="mdi:cog-outline" class="inline-icon" /> above the list. | ||
| 5. Click **Next**, select the preferred options, and click **Send to Crowdin**. |
There was a problem hiding this comment.
Send to Crowdin stays disabled until a file is selected, so it's worth mentioning the File selection as a required part of this step. The options themselves are the same as in the Strings flow, so we could just link to that list instead of "the preferred options"
| 3. Click **Sync Translations**. | ||
| </Steps> | ||
|
|
||
| For each selected language, the plugin creates or updates a mode named after the Crowdin Enterprise language code (e.g., `uk`, `zh-CN`) in the selected collections and fills it with translations. The collection's default mode is never overwritten and always holds your source text. |
There was a problem hiding this comment.
This should be "Crowdin language code" - the term is the same in both products, see enterprise/localization-resources/translation-memory.mdx:239. Also worth linking it to /developer/language-codes/ like we do elsewhere
| Additionally, you can select **Use camelCase key naming style** to generate keys in camelCase (e.g., `siteFooter`) instead of the default snake_case (e.g., `site_footer`). | ||
|
|
||
| <Aside> | ||
| Key naming settings were previously located in the plugin's **Settings** tab. They are now configured directly in the dialogs where you send strings to Crowdin, separately for the **Strings** and **Variables** tabs. |
There was a problem hiding this comment.
I would suggest dropping this one. We keep reference articles in the present tense, and the badge already marks the section as new. Something like "Key naming is configured separately for the Strings and Variables tabs, in the dialog where you send strings to Crowdin" would keep the part that's still true
2 participants
Update both the Crowdin and Crowdin Enterprise articles: