ammachado opened a new pull request, #26380:
URL: https://github.com/apache/camel/pull/26380
## Summary
Fixes the `apache/camel` `main` sources behind apache/camel-website#1746,
where 35 documentation pages have no `.md` mirror and return 404 even though
`llms.txt` links to them.
A `*` or `#` inside a single-backtick span is still parsed as a formatting
mark. Spans such as `mail.smtp.*` or `core/camel-*` pair with a later `*` and
produce mis-nested HTML like `<code>…<strong></code>…</strong>`. Browsers
tolerate it, but the website's HTML-to-Markdown step loses `article.doc` and
silently skips the page.
Changes (21 files, 100 lines, formatting only; no wording changes):
- Wildcard and `#` spans on the lines listed in the issue now use literal
monospace, e.g. `` `+mail.smtp.*+` ``, `` `+#autowired+` ``.
- `camel-jbang-mcp.adoc:189`: a backtick followed by `"` was read as a
curved-quote marker, so the span never closed. It now uses double backticks.
- `camel-jbang-tui.adoc:934`: `` `/model ` `` ends in a space, so the span
never closed. It is now `` `++/model ++` ``, which keeps the trailing space.
- Four more spans that rendered valid HTML but still showed bold text
instead of the `*` characters: the default deserialization filter patterns in
the 4.18 and 4.21 upgrade guides, and `removeHeaders("mail.smtp.*",
"mail.smtps.*")` in the 4.18 guide.
- The catalog copies of the six touched component docs are synced (they were
byte-identical to their sources before the change).
Affected pages: `security-model`, `camel-jbang-mcp`, `camel-jbang-tui`,
upgrade guides 4.14, 4.18, 4.19, 4.21, 4.22, 4.23, and the `mail`, `ai-tool`,
`mcp-server`, `mdc`, `yaml-dsl` and `opa` component docs.
## Verification
Each page was rendered with Asciidoctor.js 3.0.2 (the version in the
camel-website build) and checked with `node-html-parser`'s `valid()`, the
condition under which the Markdown generator loses the article:
- Before: all 15 sources are invalid.
- After: all 15 are valid, and no `<code>` element contains `<strong>`,
`<em>`, `<mark>` or a paragraph break.
- A before/after diff of the rendered text shows only the restored `*` / `#`
characters; intentional bold phrases that contain a code span (e.g. "A `Camel*`
header controls dispatch…") still render bold.
- All 1,076 `.adoc` sources under `docs/`, `components/`, `core/` and `dsl/`
now render valid HTML.
## Not in this PR
- The published `4.22.x` and `4.18.x` component pages need the same change
on `camel-4.22.x` and `camel-4.18.x` (follow-up backport PRs).
- The camel-quarkus, camel-spring-boot, camel-kamelets,
camel-kafka-connector and camel-karaf sources listed in the issue live in their
own repositories.
- apache/camel-website#1750 makes the Markdown generator repair malformed
pages and log them, so a regression shows up in the build log instead of as a
404.
🤖 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]
