davsclaus opened a new issue, #1771:
URL: https://github.com/apache/camel-website/issues/1771
## Description
`scripts/generate-offline-bundle.js` zips only
`components/<version>.x/*.md`, `manual/*.md`, the catalog JSON and `llms.txt`
(`VERSION_DIRS` and `SHARED_DIRS`). With #1762 and #1763 the site also
publishes a Markdown mirror of the website pages
(`what-is-apache-camel/index.md`, `when-to-use/index.md`, `trust/index.md`,
`camel-dna/index.md`, `community/**/index.md`, …) and of every blog post
(`blog/<year>/<month>/<post>/index.md`, listed in `blog/index.md`). None of
that is in the offline bundle, so an agent working from the zip cannot read the
first-reader pages or the blog, which is where the project explains its
reasoning at length (security response, AI tooling, case studies). The
`llms.txt` inside the bundle links to them by absolute URL, so offline they are
dead links.
This is the third proposal item of #1764 ("Include the website pages'
Markdown in the bundle"), split out because it depends on #1769 and #1770.
## Expected Behavior
The bundle contains the website-page and blog-post Markdown, so the "Start
here" pages and the blog index in `llms.txt` work offline.
## Proposal
- Add the website pages to `SHARED_DIRS` in
`scripts/generate-offline-bundle.js` (they are not versioned):
`what-is-apache-camel`, `when-to-use`, `trust`, `camel-dna`, `community`, plus
`blog` (`blog/index.md` and `blog/**/index.md`). Only `.md` files are zipped,
so images do not come along; a post's image links then point at the online
site, which is acceptable.
- Update the directory listing in the "Offline documentation bundles"
section of `llms-txt-template.md` and in `README.md` ("What the workflow does").
- Re-run the bundle workflow for 4.22 and 4.18 so the published zips pick
the files up.
## Additional Context
Size check: the 244 post `.md` files are 2.0 MB uncompressed and compress
well; the current 4.22 bundle is 6.3 MB.
--
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]
