davsclaus opened a new issue, #1762:
URL: https://github.com/apache/camel-website/issues/1762

   ## Summary
   
   `llms.txt` says every page is available as Markdown by replacing `.html` 
with `.md`. That is true for the Antora documentation pages (components, 
manual) but not for the Hugo website pages. Checked on 2026-09-17:
   
   | URL | Status |
   |---|---|
   | https://camel.apache.org/components/next/languages/simple-language.md | 
200, text/markdown |
   | https://camel.apache.org/manual/getting-started.md | 200, text/markdown |
   | https://camel.apache.org/what-is-apache-camel.md | 404 |
   | https://camel.apache.org/what-is-apache-camel/index.md | 404 |
   
   The same applies to `when-to-use`, `trust`, `camel-dna`, `download`, 
`tooling`, `projects`, `community` and the blog (blog posts are a separate 
issue).
   
   ## Cause
   
   `gulp/tasks/generate-markdown.js` globs `public/**/*.html` with `ignore: 
['public/404.html', 'public/**/index.html']`. Hugo renders every page as 
`<dir>/index.html` (pretty URLs), so every website page is skipped. The 
extractor itself would already cope: it falls back from `article.doc` to 
`main`, and the Hugo single-page layout renders the content inside `<main>`.
   
   ## Proposal
   
   - Include the Hugo pages: drop the blanket `index.html` ignore and instead 
skip only the list and section pages (or handle those separately).
   - Publish the mirror at a predictable path, for example 
`/what-is-apache-camel.md` next to `/what-is-apache-camel/`, and document the 
rule in `llms.txt`.
   - Add the resulting pages to the list that `llms.txt` is built from, so an 
agent can find "What is Camel", "When to use Camel", the trust page and the 
Camel DNA page as Markdown.
   
   These pages are the ones written for a first-time reader, human or AI, so 
they are the ones an assistant most needs to be able to read as plain text.


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