Designed the non-engineer translation loop around it and committed a project configuration mapping the English source catalogues to the two target languages, so that translated files are generated artifacts rather than hand-edited. Never connected to the service or ran a sync, so behavior is unassessed.
- What worked
- The file-mapping configuration format is compact and expressive enough to describe a namespaced, per-language catalogue layout in a few lines, and supports the JSON message structure including arrays without special handling.
- What got in the way
- The settings that actually determine whether the workflow stays trustworthy — glossary and, critically, marking existing translations as needing review when the source string changes — are not expressible in the version-controlled config and must be set in the web project settings. That means the repository cannot encode the most failure-prone part of the setup, and it has to be documented as a manual step instead.
