docs: add bilingual site map pages and embed them in READMEs#127
Conversation
- **Add** docs/site-map/site-map.zh-TW.html — standalone tree-diagram site map compiled from the 17 feature specs (7 nav areas, 13 pages, sub-tabs/steps, access-level badges), styled with the Label Suite design tokens, fixed light theme, self-contained (no external assets) - **Add** docs/site-map/site-map.zh-TW.png — full-page Playwright snapshot (1440px) for README embedding, since GitHub does not render repo HTML in READMEs Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- **Add** docs/site-map/site-map.en.html — English counterpart of the site map tree diagram, fully translated (section names, pages, sub-tabs, access badges, hover descriptions) with English line-height 1.6 - **Add** docs/site-map/site-map.en.png — full-page Playwright snapshot (1440px) for README embedding Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- **Embed** the English site map PNG in README.md as a new "Site Map" section after System Workflow, linking to the standalone HTML version - **Embed** the Traditional Chinese site map PNG in README.zh-TW.md after the motivation section, linking to its standalone HTML version Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
There was a problem hiding this comment.
This documentation PR adds bilingual site map pages with clean implementation. The HTML files are well-structured with proper accessibility attributes, consistent design tokens, and self-contained styling. Both README updates correctly reference the new assets. No blocking issues found—ready for merge.
You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.
Purpose
Add a spec-derived site map (Traditional Chinese + English) under
docs/site-map/and surface it in both READMEs so visitors can grasp the full page structure at a glance.Reason
The 17 feature specs define 13 pages across 7 sidebar navigation areas, but there was no single visitor-facing overview of the site structure. GitHub does not render repo HTML inside READMEs, so each map is embedded as a PNG snapshot with a link to the standalone interactive HTML version.
Result
site-map.zh-TW.html(fully Traditional Chinese) andsite-map.en.html(fully English); self-contained, fixed light theme, Label Suite design tokensChanged Files
docs/site-map/site-map.zh-TW.htmldocs/site-map/site-map.zh-TW.pngdocs/site-map/site-map.en.htmldocs/site-map/site-map.en.pngREADME.mdREADME.zh-TW.mdTest Plan
Notes
npx playwright screenshot --full-page --viewport-size=1440,900 <file-url> <out.png>(fromdesign/prototype/) whenever the site map HTML changes.specs/STATUS.md2026-07-22; the deferred Help button (shared-018) is intentionally excluded.Impact Scope
docs/site-map/)Related
None
🤖 Generated with Claude Code