Aias00 opened a new pull request, #1123:
URL: https://github.com/apache/shenyu-website/pull/1123

   ## Summary
   - set 2.7.1 as the current website docs version and keep 2.7.0.3 as a 
historical version
   - refresh current docs and zh i18n entries from the local Apache ShenYu 
repo, including missing MCP, AI, proxy, security, observability, namespace, and 
scale pages
   - fix blog author/truncate/duplicate route/zh plural warnings plus broken 
links and broken anchors across current and historical docs
   - preserve legacy `namepsace` URLs with a static compatibility page while 
keeping the typo out of generated docs sidebars
   
   ## Review notes
   - `namepsace` compatibility is client-side static redirection, not an HTTP 
301/302, because the site currently has no redirect plugin or server redirect 
layer
   - blog/news author and truncation warnings are ignored in config to keep 
existing content buildable; this does not validate metadata quality
   - `src/pages/versions.tsx` still has a hardcoded current version label that 
can drift if future version metadata changes are not kept in sync
   
   ## Verification
   - `COREPACK_ENABLE_PROJECT_SPEC=0 yarn build`
   - grepped the build log for broken links, broken anchors, duplicate routes, 
blog metadata warnings, zh plural warnings, WARNING, and ERROR
   - verified production serve routes for 
`/docs/user-guide/admin-usage/namepsace`, 
`/docs/user-guide/admin-usage/namespace`, 
`/zh/docs/user-guide/admin-usage/namepsace`, and 
`/zh/docs/user-guide/admin-usage/namespace`
   - checked generated sidebar data so `namepsace` no longer appears in current 
docs sidebar
   
   ## Not tested
   - full manual copy review for every historical-version document touched by 
mechanical link and anchor normalization


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