dengliming opened a new issue, #1138:
URL: https://github.com/apache/shenyu-website/issues/1138

   Issues found in the **current** (unversioned) docs, `community/`, `helm/` 
and `event/`.
   
   ## Missing images
   
   - `docs/developer/spi/custom-metrics-monitor.md:63` → 
`/img/shenyu/custom/custom-metrics-monitor-en.jpg`
   - 
`i18n/zh/docusaurus-plugin-content-docs/current/developer/spi/custom-metrics-monitor.md:60`
 → `.../custom-metrics-monitor-zh.jpg`
   
   Nothing matching `*metrics-monitor*` exists under `static/img`.
   
   ## MDX swallows `{}` / `${}`
   
   MDX treats `{}` as an empty expression and drops it:
   
   - `event/2.7.0-release.md:84` (+ zh copy `:84`): `replace log %s -> {}.` 
renders as `-> .`
   - `docs/plugin-center/mock/mock-plugin.md:103` and `:160`: `${}` renders as 
`$` (the zh doc already wraps it in backticks)
   
   ## Wrong links
   
   - `docs/developer/custom-plugin.md:342`: `[...](#Single Responsibility 
Plugin in Multiple Languages)` — anchor with spaces; should be 
`#single-responsibility-plugin-in-multiple-languages`.
   - `docs/developer/custom-plugin.md:92` links 
`https://shenyu.apache.org/docs/next/design/wasm-plugin-design/` (+ zh `:97` 
with `/zh/docs/next/`). `/docs/next/` is not served. Use 
`/docs/design/wasm-plugin-design`.
   - `helm/index.md:98,99,250,251`: English page links to 
`https://shenyu.apache.org/zh/docs/user-guide/property-config/{gateway,admin}-property-config`.
 Drop `/zh`.
   - `community/2-issue-pr.md:74` (+ zh): 
`https://github.com/dromara/shenyu/labels` → `apache/shenyu`.
   - Release-guide email templates (all 7 en guides under 
`community/release-guide/` and their zh copies):
     - `https://shenyu.apache.org/community/release-guide/#check-release` 
(`main-release-guide.md:337`) → needs the page segment, e.g. 
`/community/release-guide/main-release-guide#check-release`.
     - 
`https://shenyu.apache.org/community/shenyu-{nginx,wasm,client-golang,client-python,client-rust,client-dotnet}-release-guide/#check-release`
 are missing the `release-guide/` segment 
(`16-shenyu-nginx-release-guide.md:306`, `17-shenyu-wasm-release-guide.md:331`, 
`15-shenyu-client-dotnet-release-guide.md:311`, …).
     - `https://shenyu.apache.org/docs/index/` (`main-release-guide.md:535`, 
`16-shenyu-nginx-release-guide.md:446`) → `/docs/`.
     - English guides hard-code `https://shenyu.apache.org/zh/download/` and 
`/zh/news` (14 lines, e.g. `main-release-guide.md:476,492`).
   - `community/5-committer.md:113,116,147,164,165` (+ zh): 
`http://www.apache.org/...` → https.
   - `i18n/zh/docusaurus-plugin-content-docs/current/index.md:39` loads 
`https://shenyu.apache.org/img/shenyu/activite/shenyu-xmind.png` although the 
file exists locally; use `/img/...`.
   
   ## Old org / brand leftovers
   
   - `i18n/zh/.../current/index.md:157` star-history chart uses 
`apache/incubator-shenyu`.
   - 
`i18n/zh/docusaurus-plugin-content-docs-community/current/10-user-registration.mdx:22`
 links `github.com/apache/incubator-shenyu/issues/68`; 
`12-create-repository.md:12,18` uses `incubator-shenyu-helm-chart` as example.
   - `docs/quick-start/quick-start-dubbo.md:117-127`, 
`quick-start-sofa.md:75-86` (+ zh, ~46 lines): sample logs still show 
`org.dromara.shenyu.examples...` class names.
   
   ## Frontmatter
   
   - `docs/user-guide/admin-usage/{instance,namespace,scale}.md` (+ zh) have no 
frontmatter at all.
   - `shenyuNginx/index.md` has no frontmatter and starts with a setext H2; 
page title becomes "index".
   - `sidebar_position` collisions in `docs/deployment` (en): 
`deployment-local`/`deployment-quick` both 1, 
`deployment-docker`/`deployment-docker-compose` both 3, 
`deployment-aapanel`/`deployment-custom` both 6 (zh has the first two too).
   - `community/2-issue-pr.md:84` contains a literal `[TODO-LIST]` label.
   


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