Help Wanted · Localization (en, ja, zh)

[contexa73]

Help Wanted · Localization (en, ja, zh)

Labels: help-wanted, documentation, good-first-issue
Assignee: @contexa73
Type: Community contribution

Background

Contexa documentation, error messages, and operator UI currently support Korean (ko) and partial English (en). To reach the broader Asia-Pacific developer audience, we want first-class Japanese (ja) and Simplified Chinese (zh) translations.

This issue is intentionally split into small contributions so first-time contributors can take on a single file at a time.

Surfaces to translate

Surface	Files	Difficulty
Documentation site	contexa-docs/src/docs/**/*.html	Medium
Operator UI message bundle	contexa-iam-enterprise/src/main/resources/i18n/messages-enterprise_*.properties	Easy
Decision rationale templates	contexa-core/src/main/resources/prompts/*.txt	Hard (LLM prompt sensitivity)
Error messages	contexa-common/src/main/resources/i18n/messages_*.properties	Easy
README	README.md (root)	Easy

Style guide

• Operator-facing strings: use plain operational language, not internal engineering terms (see policy: i18n plain language rule)
• Technical product terms (CONTEXA, Spring Boot, Zero Trust, JWT, OAuth2) remain in their original spelling
• Keep ${placeholder} tokens intact — only translate surrounding text

How to contribute

1. Pick one file from the table above
2. Comment "I'll take {filename}" so two people don't duplicate work
3. Open a PR with the new locale file (*_ja.properties or *_zh.properties)
4. Native speaker review will be requested before merge

Acceptance for each PR

• All keys translated (no fallback to source language)
• No missing ${placeholder} tokens
• Native speaker review approval
• No machine-translation artifacts (review carefully)

Reference

• Existing Korean bundle as reference: messages-enterprise_ko.properties (~8,461 lines)
• Style precedent: i18n plain-language operating principle (avoids internal design vocabulary)