[chore](i18n) Remove Japanese docs and the EN->JA translation pipeline - #4075
Merged
Conversation
Drops the Japanese locale from the website entirely. Removed: - `ja-source/` (5703 files), the Japanese doc source tree - `ja-build/`, the prebuilt Japanese site copied into `build/ja` at deploy - `scripts/i18n/`, all 9 scripts, each added by the original `feat(website): i18n ja (apache#3468)` commit and referenced only by the translation workflow - `.github/workflows/manual-i18n-translate-workflow.yaml`, the EN->JA translation pipeline Deploy workflows (`cron-deploy-website.yml`, `manual-deploy-website.yml`) no longer guard on `ja-build` or copy it into `build/ja`. Their build step already passed only `--locale en --locale zh-CN`. Site config: `locales` is now `['en', 'zh-CN']`; the `ja` localeConfig, `/ja/search` sitemap exclusion, `ja` search language, and `ja/docs` route bases are gone, along with the ja branches in `custom-docusaurus-plugin.js`, `update_search_hash.js`, the TOC UI strings, and the `start:ja` / `write-translations:ja` package scripts. `patch-search-tokenize.js` loses its two Japanese-only node_modules patches; the four locale-aware search patches stay, since zh-CN still needs them. Docs governance: ja locale, `ja_source` content root, and the `i18n-sync-locale-candidate` rule are removed from the rules, manifest, and linters, with matching test updates. `yarn docs-governance:test` passes 37/37. The locale dropdown's "Coming Soon" badge mechanism is kept; its locale set is now empty since `ja` was its only member. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
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.
Versions
(Applies to all versions: the Japanese tree carried
current/4.x/3.x/2.1copies.)Languages
Japanese only — Chinese and English content are untouched.
What this does
Removes the Japanese locale from the website entirely, together with the pipeline that produced it.
Deleted
ja-source/— 5,703 files, the Japanese doc source treeja-build/— the prebuilt Japanese site copied intobuild/jaat deploy timescripts/i18n/— all 9 scripts. Every one was added by the originalfeat(website): i18n ja (#3468)commit, and nothing outside the translation workflow referenced them..github/workflows/manual-i18n-translate-workflow.yaml— the EN→JA translation pipelineDeploy workflows
cron-deploy-website.ymlandmanual-deploy-website.ymlno longer guard onja-buildor copy it intobuild/ja. Their build step already passed only--locale en --locale zh-CN, so nothing else about the build changed.Site config
docusaurus.config.js:locales→['en', 'zh-CN']; dropped thejalocaleConfig, the/ja/searchsitemap exclusion,'ja'from the search languages, and theja/docs/ja/courseroute basesconfig/custom-docusaurus-plugin.js,scripts/update_search_hash.js, and thestart:ja/write-translations:japackage scriptssrc/theme/TOC/index.tsx: dropped the Japanese UI-string branchscripts/patch-search-tokenize.js: removed the two Japanese-onlynode_modulespatches (kana tokenizer preference, zh+ja mixed-mode tokenizer). The four locale-aware search patches stay — zh-CN still needs them.Docs governance
The
jalocale, theja_sourcecontent root, and thei18n-sync-locale-candidaterule are removed from.docs-governance/rules.yml,manifest.js,lint-links.js,lint-seo.js, andlint-i18n-sync.js, with matching test updates.i18n-sync-policy.md,translation-glossary.yml, theexceptions.ymlexample, and the PR template's Japanese checkbox are updated to match.website-quality-governance/broken-links-baseline.md: theja-source/rows are dropped and its 502 internal errors subtracted from the internal tables (exact per-root counts from the same scan). The externalinfocount has no per-root breakdown and still reflects the original scan; the file now says so.Notes for reviewers
Two deliberate judgment calls:
jawas its only member, soCOMING_SOON_LOCALESis now an empty set; the markup and styles are untouched so a future locale can use it.src/utils/tokenize.tsis left alone. Its["ja", "jp", "th"]list is a vendored copy of the upstream search-plugin util (added well before the Japanese work), andjp/thare equally unused there. Removing justjawould be arbitrary.Docs Checklist
yarn docs-governance:testpasses 37/37. No site build was run locally.🤖 Generated with Claude Code