[zoltan-baba]

Summary

Adds the Japanese locale for the docs and updates the translation pipeline so new English changes translate correctly on their own. Nothing in docs/ or src/partials/ changes; English content is untouched.

Translated content (i18n/ja/)

• 451 pages and 45 shared partials across Bitrise CI, Platform, Release Management, Build Hub, RDE, Insights and Build Cache, plus the changelog (translated once, shared).
• Frontmatter titles/descriptions and hub-page text are translated.
• Sidebar labels, navbar, "See also", breadcrumbs and search placeholders are translated.
• Generated API reference docs are intentionally not translated.

Pipeline (.github/scripts/translate_docs.py and helpers)

• Every translated heading keeps its English {#id}, so anchor links still work (scripts/heading_ids.py). A mid-line anchor is moved to the end of the heading.
• Frontmatter and JSX hub-page strings are translated (scripts/translatable_strings.py).
• Partials are translated first and Japanese pages import the Japanese copy.
• Fix for bold text that ends in italic (***), which broke MDX.
• A page whose English only changed in whitespace is not re-translated, and each run prints a plan line first.
• A warning appears when the model returns a heading untranslated.
• New scripts/translate_ui_strings.py plus a workflow step translate new sidebar labels and UI strings, using localization/ja-ui-strings.yaml.
• Terminology: one rendering for AI agent, product names and warm pool stay in English.

Site code

• docusaurus.config.ts: list-context partials expand from the Japanese copy under /ja/.
• Hardcoded UI strings (navbar search, "See also", breadcrumbs, portal page) now go through translate().

Not verified

• The pipeline has not run against the real API or in CI. All translations here came from Claude subagents with the same prompt. The workflow stays off until ANTHROPIC_API_KEY exists. I'd run it on a small test PR first.
• No native-speaker review of the Japanese text.

Testing

• Unit tests for the new and changed scripts pass (scripts/test_*.py).
• npm run build passes for both locales. The 5 broken anchors per locale come from main and are the same in English.
• scripts/heading_ids.py --check is clean.
• The translated site was checked in a local build and served preview, with language switching.
• Search and the cookie banner only work in production builds, so neither was tested locally.

Known gaps

• A heading that is only partly English is not detected.
• JSX hub strings only translate when each prop sits on its own line.
• A broken link such as a doubled ](](url) is not detected; one case was fixed by hand.

🤖 Generated with Claude Code

[github-actions]

Preview: https://ja-translation-test.bitrise-docs.pages.dev

[ilanazholobovsky]

Reviewed the JA locale and the translation pipeline end to end. The structure is in great shape: all 1,834 heading anchors match English, no code blocks changed, docs/ untouched, and the ja build passes. Really solid work.

I found a few defects, most of them caused by how the pipeline protects English terms, and I've opened two follow-up PRs into this branch:

#335: Repair structural defects in the JA docs (merge first)

• Broken link markup on 14 pages. Root cause: relative_link_target masked the ] together with the target, so the model saw [text⟦p7⟧ with no closing bracket. 33 of 3,189 internal links broke, against 0 of 1,143 external ones.
• 227 UI labels and Step names half-translated in bold (e.g. Newタスク), restored to the exact English.
• 324 lost spaces between English words (iOScode signing), restored.
• 2 stale sidebar_position values; "code signing" kept in English.

#338: Harden the pipeline against structural breakage (stacked on #335)

• Fixes the masking at the cause, and adds structure_issues() next to verify_tokens in the retry loop and in CI. 30 problems at this branch's head, 0 after #335.
• Narrows the list-item rule in nt_terms.context_allows(), which was freezing phrases like "Log in" mid-sentence.
• Includes your fix/translate-ja-docs-diff-range commit (authorship kept), plus a few workflow and change-detection fixes.

Both PRs only make structural and keep-English changes, with no new Japanese wording. Each commit can be dropped on its own. Decisions that are yours to make are listed in #338 under "Decisions for Zoli".

Not covered: #331's changelog changes. Once it merges, the pipeline re-translates the changelog automatically, and I'll open a small PR to make its filter labels translatable.