[EPIC] documentation localization rollout

[bnbong]

Requesting other issue

Documentation localization rollout for all supported docs locales.

Why

FastAPI-fastkit currently builds documentation for these locales:

• English (en) - canonical source of truth
• Korean (ko)
• Japanese (ja)
• Chinese (zh)
• Spanish (es)
• French (fr)
• German (de)

The docs site already documents that English is the source of truth and that translated pages may lag behind or fall back to English.

Goals

• Translate high-value docs across all supported non-English locales
• Establish a shared multilingual glossary before large-scale translation
• Land translations in small reviewable batches instead of one large PR
• Keep terminology consistent across locales and across batches
• Keep docs/en/ as the canonical source of truth
• Update translation completeness/status as batches land

Scope

• Locale rollout for:
  • ko
  • ja
  • zh
  • es
  • fr
  • de
• Translation workflow and glossary alignment
• Translation status updates
• Documentation-only changes

Non-Goals

• Product/runtime behavior changes
• Rewriting English docs as part of translation work
• Shipping all locale work in a single PR
• Claiming full parity before each locale is actually reviewed

Recommended rollout

1. Establish glossary and translation workflow baseline
2. Translate core user-guide pages for each locale
3. Translate remaining user-guide and tutorial pages
4. Translate contributing/reference/changelog pages as needed
5. Update translation status after each landed batch

Release / merge policy

• English remains the source of truth
• Each translation PR should stay small and reviewable
• AI-generated translations require human review before merge
• Translation status must reflect actual repository state

Acceptance Criteria

• A glossary/workflow baseline issue is completed
• Each non-English locale has a tracker issue
• Translation work lands in multiple small PRs
• uv run mkdocs build passes for every translation PR
• Translation status docs remain aligned with the repository state

[ShuwenWuCitrus]

Hi there, I’m a software engineering student and an English–Chinese translator. I’d love to contribute!

[bnbong]

Thanks so much, @ShuwenWuCitrus — I’d be very happy to have your help on the Chinese localization work.

I’ve decided to track translation work by target language, so I opened the dedicated Chinese localization issue here: #61

The Chinese docs should live under:

• docs/zh/

Helpful references:

• Translation guide: https://github.com/bnbong/FastAPI-fastkit/blob/main/docs/en/contributing/translation-guide.md
• Translation status / locale policy: https://github.com/bnbong/FastAPI-fastkit/blob/main/docs/en/reference/translation-status.md
• Localization EPIC: [EPIC] documentation localization rollout #59
• Localization baseline: [DOCS, I18N] Establish multilingual glossary and translation workflow baseline #60
• Chinese localization issue: [DOCS, I18N] Chinese documentation localization #61

A few important notes:

• English (docs/en/) is the source of truth.
• Please preserve markdown structure, headings, links, code fences, tables, and admonitions.
• Commands, file paths, env vars, template ids, and product names such as FastAPI-fastkit and fastapi-domain-starter should stay in English.
• You do not need to translate everything in one PR — small, reviewable PRs are preferred.
• If any English wording feels ambiguous, please feel free to ask instead of guessing.

Please feel free to start from that issue, and open a PR whenever you're ready.

If you have any questions about technical meaning, wording, or the documentation itself, please leave a comment anytime in the issue or in your PR. I’ll be happy to help. Thanks again for contributing!