docs: expand zh-Hans documentation coverage to match the current English docs tree #1602
Description
Describe the feature
Expand and organize the Simplified Chinese docs coverage so zh-Hans stops lagging far behind the current English docs tree.
Primary docs surfaces:
website/docs/**website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/**website/i18n/README.md
Primary layer
global level
Why this layer?
This is a documentation/i18n maintenance task across the website docs tree rather than a single signal/plugin/runtime feature.
Why do you need this feature?
The current repo state shows a large English/Chinese documentation gap:
website/docscurrently has 103 Markdown docswebsite/i18n/zh-Hans/docusaurus-plugin-content-docs/currentcurrently has 23 Markdown docs- representative missing Chinese docs include:
intro.mdinstallation/configuration.mdinstallation/installation.mdoverview/semantic-router-overview.mdoverview/signal-driven-decisions.md- multiple
fleet-sim/**pages
The repo already has a documented i18n workflow in website/i18n/README.md and locale-specific site commands in website/package.json, but there is currently no dedicated GitHub issue tracking the missing zh-Hans coverage.
Additional context
Suggested acceptance criteria:
- the most user-facing English docs sections have corresponding zh-Hans pages under the current docs tree
- translated files include the required translation frontmatter documented in
website/i18n/README.md - contributors can work section-by-section without inventing a separate i18n workflow
- docs changes validate through the normal website/docs checks used by the repository
A reasonable phased approach is:
- intro + installation
- overview
- tutorials
- fleet-sim / training / proposals
This is a good help wanted docs issue. It is intentionally larger than a typo fix, so it should be split into section-sized PRs rather than treated as a one-shot newcomer task.