Best Practices
- Keep key naming conventions stable and documented
- Add context descriptions to reduce translation ambiguity
- Review AI-generated content before production usage
- Automate export/import checks in CI/CD
- Rotate API keys and enforce least-privilege scopes
Suggested Governance Rhythm
- Weekly: key hygiene and duplicate detection
- Release cycle: locale completeness and smoke tests
- Monthly: access and key rotation review
Recommended Naming Pattern
domain.feature.element.state
auth.login.button.submit
errors.network.timeout.messageLast updated on