davsclaus opened a new issue, #1607: URL: https://github.com/apache/camel-website/issues/1607
## Summary We should create a dedicated tooling page on camel.apache.org that highlights the full Camel tooling ecosystem — both built-in and third-party. Currently tooling entries are buried in the User Stories page where they don't belong. A dedicated page would make it easier for users to discover available tools, and would significantly improve AI discoverability (AI coding assistants surface content from camel.apache.org when developers ask about tooling). ## Suggested content ### Built-in Camel tooling (ships with the project) - `camel jbang` — instant development, no project setup needed - `camel dev` — hot-reload development mode - `camel run` — run Camel routes - `camel trace` — live message tracing step by step - `camel send` — send test messages to running routes - `camel test` — run tests - `camel export` — export to Spring Boot / Quarkus / standalone - `camel ai` — AI-assisted route generation - `camel tui` — terminal UI for managing and monitoring Camel - Camel MCP Server — integration with AI coding assistants (Claude Code, GitHub Copilot, Gemini CLI, Cursor, etc.) - Maven and Gradle plugins ### Third-party tooling - Apache Camel IDEA Plugin (IntelliJ) - VS Code extension pack for Camel - Camel Language Server (LSP) - Camel Debug Adapter (DAP) - Kaoto visual editor - hawt.io web console ## Follow-up Once this page exists, the Developer Tooling section should be removed from the [User Stories](https://camel.apache.org/community/user-stories/) page and replaced with a link to the new tooling page. -- 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]
