Externalizing and Translating Text

What problem does it solve?

Externalizes end-user strings into a localized resource bundle to enable translation and localization across services and templates.

Core Features & Use Cases

• Create a text.yaml bundle under resources to hold localized strings.
• Map strings to per-language keys (en, fr, es, etc.) and integrate with code.
• Update Go files and templates to load localized strings at runtime.
• Document and version the translations for consistent releases.

Quick Start

Step 1: Create a text.yaml under the resources directory of your microservice. Step 2: Identify end-user strings in Go files and templates and add entries in text.yaml with per-language localizations. Step 3: Implement loading in code using svc.MustLoadResString(ctx, "Key") and ensure templates consume the localized value. Step 4: Reference localized strings in templates via a map obtained from svc.MustLoadResStrings(ctx). Step 5: Document translation requirements in AGENTS.md and version the translation bundle.