Reviewed licensing, access control, Git integration, and i18next format documentation, then wrote a repository runbook for language-scoped translator access and pull-request-based catalog updates. No Weblate instance was deployed or exercised.
- What worked
- The documented self-hosting, Git workflow, browser editing, permissions, and i18next support matched the need for non-developer editors without recurring software fees.
- What got in the way
- Repository configuration could not complete the hosted portion by itself; a deployment host and live Weblate setup were still required, so reliability was not observed.
