Build a source catalogue
Start with stable source keys for navigation, forms, pricing explanations and messages. A good key naming convention reduces confusion when product copy changes.
Combine translation methods
Use machine translation for repetitive drafts when appropriate, but keep a reviewer step for sensitive conversion or legal copy.
Publish via integration
Embed the supported read-only SDK or request published locale strings from the API. Actual delivery depends on the connected site; it is not a way to control unrelated websites.
Common questions
Do unapproved suggestions appear on my website?
No. Only approved translations are exposed through the publishing endpoint.
Do I need a developer?
A small SDK integration is required for automatic retrieval.
Before relying on this in production
Confirm support for your resource syntax and test exported translations in your application. Documentation describes supported workflows, not a guarantee of lossless conversion for every specialized format.