morningman opened a new pull request, #4206: URL: https://github.com/apache/doris-website/pull/4206
Adds a build-time Japanese PoC behind `DORIS_ENABLE_JA=true`. Default development and production remain English/Chinese. Enabling the flag generates a Japanese homepage, Dev/4.x overview translations, a runnable Dev MDX getting-started page, and a community translation. Missing translations use the content plugin's version-specific English fallback, with a Japanese notice and `lang=en` on the body. The homepage uses stable messages with unchanged English defaults and no Chinese overrides. Japanese heading IDs match English. Links to ordinary pages beyond the homepage explicitly lead to English; content-plugin navigation stays localized. CDN and worker paths use the resolved locale base URL; an empty `DORIS_ASSET_ORIGIN` serves the new artifact's own assets. A read-only Japanese PoC workflow compares full English/Chinese and full sequential English/Chinese/Japanese builds on the same Ubuntu runner with production Node 20, the 8192 MiB Node heap, and 8 GiB additional swap. It records timings, process/system/cgroup memory, logs, browser evidence and the static site. It has no deployment steps or deployment secrets. The PR entry runs on PoC branch names before merge; manual dispatch becomes available after merge. Validation is still in progress; this PR remains a draft until evidence is available. - Passed 17 related Node tests and a source extraction check covering 283 homepage message declarations. - Saved the unmodified English/Chinese static build and rendered baseline for current/4.x plus the existing blog/community/course/release/search plugins. - `yarn typecheck` reports the same 150 distinct pre-existing diagnostic messages, with no added diagnostics in the first implementation check. - The first scoped three-language build passed. Rebuilding after correcting sample Markdown link resolution and completing the shared community prompt. - Final browser checks and the complete GitHub memory comparison are pending. Scoped macOS builds are not full CI memory evidence. Self-review against AGENTS.md: 1. Goal: provides a usable static opt-in PoC. Full browser and CI evidence remain pending; Japanese public launch stays disabled. 2. Scope: one task, four real content translations, shared homepage messages, minimal fallback UI and validation tooling. No translation service, state engine or publication change. Three existing declaration constants gain `declare` because the required translation extraction otherwise fails on their `.d.ts` file. 3. Information architecture: current and active versions remain intact. The community plugin remains separate. No English/Chinese document content, sidebar structure or existing slug is rewritten. 4. Routes and references: translated headings retain English IDs. Japanese sample links resolve within their plugin/version; ordinary-page destinations are explicitly English. Existing routes and redirects are preserved. 5. Frontend/configuration: reuse the existing layouts and all eight brand themes. The new notice uses semantic tokens; embedded visuals retain the existing theme bridge. Static hydration and mobile/theme verification are pending. 6. Verification: existing required PR checks are unchanged. The dedicated full-build probe cannot be replaced by the scoped local build; no OOM-free claim has been made yet. 7. Other issues: Japanese status/SEO/search and launch policy remain later gated tasks. Existing build link warnings and TypeScript diagnostics are recorded rather than represented as newly introduced failures. All current PoC issues must be fixed within this PR. Rollback: leave `DORIS_ENABLE_JA` unset or false; reverting this PR requires no English/Chinese content rollback. Existing cron/manual publication workflows still build only English and Chinese. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
