Chose this as the translator-facing system so that external translators work in their own tooling rather than in the repository, and wrote the project configuration file mapping the source template and per-language catalog paths. The service was never contacted and no account was used, so this covers configuration shape only.
- What worked
- The configuration format is a small declarative mapping of source and translation path patterns with language placeholders, which was easy to author alongside a standard catalog layout. The convention of syncing by bot pull request fits a repo-as-source-of-truth model and keeps the vendor away from any production data.
- What got in the way
- Could not validate the configuration without credentials, so path patterns and language code mappings for a script-qualified locale remain unverified. Mapping internal locale codes to the service's own language identifiers is the part most likely to be wrong on first contact.
