ammachado opened a new pull request, #26381: URL: https://github.com/apache/camel/pull/26381
## Summary Backport of #26380 to `camel-4.22.x` for apache/camel-website#1746: the `components/4.22.x` pages below have no `.md` mirror because they render mis-nested HTML, which the website's HTML-to-Markdown step skips. A `*` inside a single-backtick span is still parsed as a formatting mark, so spans such as `` `mail.smtp.*` `` pair with a later `*` and produce `<code>…<strong></code>…</strong>`. These spans now use literal monospace (`` `+…+` ``). Formatting only; no wording changes. Pages (the website publishes only `docs/components` and the core engine docs from this branch; the user manual comes from `main` and is fixed in #26380): - `mail-component` - `ai-tool-component` - `others/mcp-server` - `others/mdc` - `others/yaml-dsl` - `others/leveldb` The catalog copies of these docs are synced. ## Not a straight cherry-pick #26380 also touches user-manual pages that this branch does not publish, so only the component doc hunks are ported. The mail, ai-tool, mcp-server, mdc and yaml-dsl changes match #26380 hunk for hunk. **The leveldb change is new**: the component was removed from `main`, so it is not part of #26380 and has not been reviewed there. ## Verification Rendered with Asciidoctor.js 3.0.2 (the camel-website build version) and checked with `node-html-parser`'s `valid()`, the condition under which the Markdown generator loses the article: - Before: all six sources are invalid. - After: all six are valid, and no `<code>` element contains `<strong>`, `<em>` or `<mark>`. - Scanning every `.adoc` under `docs/` and `*/src/main/docs/` on this branch, these six were the only published sources that rendered invalid. 🤖 Generated with [Claude Code](https://claude.com/claude-code) on behalf of Adriano Machado (@ammachado) _This was generated by an AI agent and may contain inaccuracies. Please verify before relying on it._ -- 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]
