luigidemasi opened a new pull request, #120: URL: https://github.com/apache/camel-kit/pull/120
Second step of the documentation migration to camel.apache.org (follows #116): the seven **Getting started** pages of the Antora component are written. | Page | Content | |------|---------| | `getting-started.adoc` | Prerequisites, release channels, install (standalone JBang, Camel JBang plugin, snapshot, source build), upgrading, `init`, configuration layers, `doctor`, first command | | `agents.adoc` | The eight `--ai` targets: how to start the workflow in each, what `init` generates, target-specific notes, retired targets | | `greenfield.adoc` | Interview, design specification, plan, execute with its three reviews, runtime verification, validate, pipeline files, standalone stages and amendments | | `migration.adoc` | Supported platforms, `init --here`, `/camel-migrate` (and direct mode), discovery, graph analysis, the four-artifact package and the approval scope, plan/execute/verify/validate, troubleshooting | | `migration-mulesoft.adoc` | Parsed artifacts, evidence and retirement, component and proprietary connector mapping, DataWeave handling, five before/after examples | | `migration-biztalk.adoc` | Parsed artifacts, adapter mapping and MSMQ, orchestration shapes, pipelines, maps and functoids, example, manual-review list | | `migration-camel-upgrade.adoc` | Parsed artifacts and Fuse detection, component renames and HTTP consumer rule, Karaf/Blueprint, Spring XML and Java DSL paths, four examples | The text is rewritten from the standalone website and the repository documentation into the Camel documentation register. Every command, option, version and mapping was checked against `README.md`, `docs/commands.md`, `docs/user-guide.md`, `docs/antigravity.md`, `camel-kit-workflow.yaml`, `distribution.properties`, the `camel-migrate` guides and the graph parsers. Hugo shortcodes became native AsciiDoc (tabs, collapsible blocks, titled listings, literal blocks). Links into the Camel documentation use `xref:manual::` and `xref:components::` targets, which resolve once the component is registered in `apache/camel-website`. A `camel-kit-snapshot-version` attribute in `docs/antora.yml` keeps the snapshot version out of the pages. The install snippets reproduce the released 0.4.1 coordinates (`luigidemasi/camel-kit` JBang catalog, `io.github.luigidemasi` plugin GAV) and say so in a note; the source build clones `apache/camel-kit`. The README's own clone URL is tracked in #115. ### Local build ```bash # from a camel-website checkout, with a playbook that sources this branch's docs/ # plus stub `manual` and `components` sources for the three external xrefs NODE_PATH=$PWD/node_modules node_modules/.bin/antora --clean playbook.yml ``` Antora 3.2 with the Camel website UI bundle at `failure_level: warn`: 27 pages, no warnings, no absolute `camel.apache.org` links in the generated HTML. Desktop and mobile renders checked in headless Chrome. No change outside `docs/antora.yml` and `docs/modules/`; the existing `docs/*.md` files are untouched. Next: the Pipeline 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]
