Summary

• Add a manually-triggered GitHub Actions workflow (workflow_dispatch) to generate versioned offline documentation bundles
• New scripts/generate-offline-bundle.js zips version-specific .md files (components, Spring Boot starters, Kamelets, manual) into a single archive
• Upload the zip as a GitHub Release asset (e.g. camel-docs-4.18.zip under release tag docs-4.18)
• Update llms-txt-template.md to list available versioned bundles so AI agents can discover the right version

Motivation

Companies may restrict their AI coding agents from accessing the internet. A versioned offline bundle lets an agent working with Camel 4.14 download just the 4.14 docs, without needing to reach camel.apache.org.

How it works

1. After a Camel release, a maintainer triggers the workflow from the Actions tab with the version (e.g. 4.18)
2. The workflow builds the full site, then runs the bundle script to zip only version-specific .md files
3. The zip is uploaded as a GitHub Release asset — no binary files in the git repo
4. Normal website builds are unaffected — the zips live in GitHub Releases, not in the published site

Test plan

• Trigger the workflow manually with a version (e.g. 4.18)
• Verify the GitHub Release is created with the correct zip
• Verify the zip contains the expected .md files preserving directory structure
• Verify llms.txt renders correctly with the new section

🤖 Generated with Claude Code