qqeasonchen opened a new pull request, #260:
URL: https://github.com/apache/eventmesh-site/pull/260

   Syncs the restructured documentation from 
[apache/eventmesh@develop](https://github.com/apache/eventmesh/tree/develop/docs)
 (post PRs apache/eventmesh#5390, #5391, #5392, #5393) into the website as 
**version v2.0.0**.
   
   ## What's in v2.0.0
   
   28 pages mirroring the new `docs/` tree:
   
   ```
   version-v2.0.0/
   ├── introduction.md + documentation-map.md   (was index.md)
   ├── quickstart/    getting-started · configuration
   ├── feature/       19 pages — pubsub · delivery-reliability · streaming ·
   │                  lite-topic · a2a (+readiness) · offset-management ·
   │                  load-balancing · frame-protocol · control-plane ·
   │                  client-java · http-api · admin-api · observability ·
   │                  deployment · protocols · storage-spi ·
   │                  architecture-guard · connector-api-split
   └── architecture/  overview · security · redesign (English) ·
                      review/{evidence, production-ha-plan}
   ```
   
   ## Docusaurus adaptations
   
   - `sidebar_position` frontmatter per page; `_category_.json` per section 
(Quickstart / Features / Architecture / Architecture Review Records) with 
curated ordering (core features → internals → API & operations)
   - `index.md` renamed `documentation-map.md` (Docusaurus reserves the 
concept; links updated)
   - Repo-relative links that escape the versioned root (e.g. 
`../../README.md`, `../../eventmesh-runtime/conf/...`) rewritten to absolute 
GitHub `develop` URLs
   - MDX fixes: `<br>` → `<br />` in the A2A tables
   - `versions.json`: `v2.0.0` registered first → renders as **lastVersion at 
`/docs`**; all v1.x versions and the `next` (1.x dev) docs are untouched
   
   ## Verification
   
   - `npm run build` succeeds for **en + zh locales**, 0 broken links
   - All 164 internal `.md` links within the versioned tree resolve
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to