Lexique
Guides

A practical translation key workflow

A practical guide to naming translation keys, adding context, tracking missing locales, and keeping multilingual product copy shippable.

Use stable keys

A translation key should describe the product intent, not the exact English copy. This makes copy iteration safer because the key can stay stable while values change by locale.

checkout.payment.submit
checkout.payment.cancel
auth.login.error.invalid_credentials

Add context before review

  • Describe where the copy appears.
  • Tag keys that need legal, product, or localization review.
  • Track missing values by locale before release.
  • Keep the exported bundle aligned with the repository format.

Avoid spreadsheet drift

Spreadsheets are useful for early review, but they become risky when they drift from repo files. Lexique is designed to keep context, coverage, and exportable values in one workspace.