moonming opened a new pull request, #2066:
URL: https://github.com/apache/apisix-website/pull/2066

   ## Why
   
   Follow-up to #2065. That PR removed the Showcase / Code Samples / Help pages 
and the Roadmap link, but the cleanup was applied to the **website** workspace 
only. This site is built from four Docusaurus workspaces (`website`, `doc`, 
`blog/en`, `blog/zh`) merged by `scripts/generate-website.js`, and the footer + 
zh i18n are **swizzled per workspace** — so the `doc` and `blog` copies still 
carry the removed entries. Because every workspace sets `onBrokenLinks: 'log'`, 
the leftover links don't fail the build.
   
   Result on current master: every `/docs/*` and `/blog/*` page footer still 
shows a **Showcase** link (now 301-ing to home) and a **Roadmap** link to 
`apisix/milestones`.
   
   ## What this changes
   
   - `doc/src/theme/Footer/index.tsx`, `blog/src/theme/Footer/index.tsx` — drop 
the Showcase + Roadmap footer entries (mirror the website footer, now Blog + 
Plugin Hub only)
   - `doc/i18n/zh/code.json`, `blog/i18n/zh/code.json` — drop the now-unused 
`showcase.website.*` and `help.website.*` strings
   - `doc/i18n/zh/docusaurus-theme-classic/navbar.json`, `blog/.../navbar.json` 
— drop the orphaned `item.label.Showcase` / `item.label.Help` keys (navbar 
items already removed from the shared `config/navbar.js` in #2065)
   - `website/static/img/documents.png`, `community.png` — orphaned; only the 
removed help page referenced them
   
   ## Verification
   
   - `blog:en` and `blog:zh` compile cleanly; built output contains no 
`/showcase` or `milestones` links
   - All four edited i18n JSON files parse as valid JSON
   - grep across `doc/` and `blog/` shows zero remaining references to the 
removed pages/links/keys
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
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]

Reply via email to