luigidemasi opened a new pull request, #123: URL: https://github.com/apache/camel-kit/pull/123
Fourth step of the documentation migration to camel.apache.org (follows #116, #120 and #121): the seven **Architecture** pages of the Antora component are written. | Page | Content | |------|---------| | `architecture.adoc` | The four layers, "the prompt is the product" and the Ship exception, progressive disclosure and context isolation, the orchestration model, the equalization layer and traits, the contract tests, the key design decisions | | `skills.adoc` | The thirteen skills in four tiers, the shared guides, the skill structure and front matter semantics per agent, progressive disclosure, context authority, target generation and traits, adding a skill | | `mcp.adoc` | The three servers and their launch configuration, response authority, version binding, the Camel catalog tool groups, the Citrus server, fallback (merges the former MCP integration and Camel MCP pages) | | `knowledge.adoc` | Server release, the seven tools and the five-tool workflow allowlist, the search pipeline and local models, what is indexed, index distribution and cache, rebuilding, modules, the `camel-knowledge` skill | | `graph.adoc` | How the graph is built (nine parsers, two post-processors), the fifteen commands, dependency-injection-aware analysis, migration context, research background, where the graph is used; with the graph visualization image | | `eitl.adoc` | The environment probe, the verification loop, re-planning and promotion, the closed loop, the comparison with linear generation | | `forage.adoc` | Availability and version mapping, the configuration ladder, naming, custom bean construction, catalog checks, dependencies per runtime | The text is rewritten from the standalone website and the repository documentation into the Camel documentation register. Every claim was checked against `docs/architecture.md`, `docs/agent-architectures.md`, `docs/commands.md`, the shared guides, the workflow manifest, the graph and generator sources, `distribution.properties` and the camel-kit-knowledge repository at its 0.0.2 tag (tool names, index manifest, models, bundled catalog). Hugo shortcodes and the raw HTML grids of the old pages became native AsciiDoc; the closed-loop diagram is a text listing. `docs/antora.yml` gains `camel-quarkus-version`, `quarkus-platform-version`, `forage-version` and `citrus-version` attributes, kept in step with `distribution.properties`, so the pages carry no hardcoded versions. `docs/modules/ROOT/images/graph-visualize.png` is the image the old site used. ### Local build Antora 3.2 with the Camel website UI bundle at `failure_level: warn`, with stub `manual` and `components` sources for the external xrefs: 27 pages, no warnings, no absolute `camel.apache.org` links in the generated HTML. Desktop and mobile renders checked in headless Chrome. Two corrections touch pages merged earlier. Wildcard literals such as `*.yaml` or `/camel-*` inside backticks were paired into bold by the AsciiDoc quotes substitution and lost their asterisks in the rendered HTML (the production minifier repairs the tag nesting but not the characters); every such span across the component is now a passthrough, forty in all. The verification page now says that Qwen Code and OpenCode keep the runtime verification in their primary executor, as their traits require. One finding of the local review concerns a shipped guide rather than these pages: `skills/shared/forage.md` states that environment variables and system properties cannot address a named bean's key, but Forage 1.6.1 resolves `FORAGE_MYDB_JDBC_URL` and the `forage.myDb.jdbc.url` system property (checked against the published sources). The page documents the library's behaviour; the guides are tracked in #122. No change outside `docs/`; the existing `docs/*.md` files are untouched. Next: the Reference and contributing pages, the last group. -- 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]
