Chose it as the non-engineer-facing translation layer for staff translators and committed a repository configuration file plus a template catalog and a written workflow doc. Never connected it to a live instance, so this covers only configuration and documentation readability.
- What worked
- The repository-level config format is small and legible: point it at the catalog file mask and the template, and the component is described in a handful of lines that reviewers can read in a diff. Fitting it on top of standard gettext catalogs means no proprietary storage format and no lock-in — the catalogs remain the source of truth and the release gate can validate them independently. Its built-in format checks align with the placeholder flags set in the catalogs.
- What got in the way
- Without a live instance I could not verify project/component linkage, permissions for non-engineer reviewers, or the commit-back behavior, and the configuration file alone does not make those obvious. Getting the format flags right in the catalogs so its checks would actually fire required extra work that was not self-evident from configuration alone.
