feat: add Japanese (ja) translation of the guide (content/ja) - #4
Merged
Merged
Conversation
Full ja translation of all 32 content/*.md files (front matter + 5 modules). Proper nouns, protocol names, code, field names, paths and URLs kept verbatim; descriptive concepts, prose, guideline/module titles and section headers localized. Human-readable sample values (manifest/JSON-LD descriptions, FAQs, example utterances) localized; keys/enums/slugs/@types and the Acme placeholder kept. llms.txt example headers localized to Japanese per i18n convention. Validator scopes to top-level content/, so content/ja/ does not affect it.
yehonatanz
approved these changes
Jun 10, 2026
|
Michael Lugassy (Michael-Lugassy-Forter)
added
blocked
Michael Lugassy (Michael-Lugassy-Forter)
merged commit Jun 10, 2026
1b86a8d
into
main
3 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
asana: https://app.asana.com/1/7840801737159/project/23095211578528/task/1213001508748468?focus=true
What does this PR change?
Adds a complete Japanese translation of the guide under
content/ja/— all 32 markdown files (front matter, the five module overviews, and 25 guidelines). Purely additive: no English files are modified.Which guideline(s) are affected?
None are modified. This adds a Japanese mirror of every page —
00-toc,01-introduction, the fivemN-0overviews, and all 25 guidelines (m1-1…m5-4). Filenames match the English set 1:1, so relative cross-references (./mX-Y-*.md) resolve withincontent/ja/.Translation policy
概要と理由/スコアリング/手順/参考資料/Forter による支援), and human-readable sample values (manifest/JSON-LD descriptions, FAQ Q&A, example utterances) — while keeping keys/enums/slugs/@types and theAcmeplaceholder.Forter エージェンティック・オーケストレーション・スイート(Forterkept Latin).llms.txtexample section headers localized to Japanese, per llms.txt i18n convention (the spec prescribes structure, not language; native-language file per site version). Header cross-refs inm2-2/m2-4/m5-4updated to match.Checklist
titlein frontmatter (titles localized in lockstep)概要と理由/スコアリング/手順/参考資料, optionalForter による支援)forterApplies↔Forter による支援in sync (verified programmatically, 0 violations)npm run validatepasses — validator scopes to top-levelcontent/, socontent/ja/doesn't affect CI; frontmatter structural keys unchanged (onlytitlelocalized)