Copilot commented on code in PR #1740:
URL: https://github.com/apache/camel-website/pull/1740#discussion_r3941520054
##########
antora-ui-camel/src/partials/nav.hbs:
##########
@@ -1,6 +1,14 @@
<div class="nav-container"{{#if page.component}}
data-component="{{page.component.name}}" data-version="{{page.version}}"{{/if}}>
<aside class="nav" aria-label="Side menu">
<div class="panels">
+ <div class="nav-search">
+ <div class="navbar-search results-hidden">
+ <input id="search" class="search" placeholder="Search the manual"
autocomplete="off" maxlength="200">
Review Comment:
The search field has no accessible name; a placeholder is not a persistent
label and is not sufficient for assistive technology. Add an explicit
`aria-label` (or a visually associated `<label>`) so keyboard and screen-reader
users can identify the control.
##########
data/tooling.yaml:
##########
@@ -0,0 +1,139 @@
+# Tooling (/tooling/): drives layouts/tooling/list.html
+
+lead: >-
+ Apache Camel ships with a rich set of built-in developer tools and is
+ supported by a growing ecosystem of third-party tooling. Whether you
+ prefer the command line, an IDE, a visual editor, or AI-assisted
+ development — there is tooling to help you build, test, debug, and
+ manage your Camel integrations.
+
+cliDocs: /manual/camel-jbang.html
+tuiDocs: /manual/camel-jbang-tui.html
+
+cliCommands:
+ - cmd: camel run
+ desc: Run Camel routes from source files (Java, YAML, XML, etc.) with
automatic classpath management
+ - cmd: camel dev
+ desc: Run in developer mode with hot-reload — changes are picked up
automatically without restarting
+ - cmd: camel trace
+ desc: Live message tracing, step by step through your routes to see how
messages are processed
+ - cmd: camel cmd send
+ desc: Send test messages to running Camel routes for quick testing and
debugging
+ - cmd: camel test
+ desc: Run tests for your Camel routes (a plugin, installed with camel
plugin add test)
+ - cmd: camel export
+ desc: Export your Camel project to Spring Boot, Quarkus, or standalone
Java for production deployment
+
+aiTools:
+ - name: Camel Kit
+ url: https://github.com/luigidemasi/camel-kit
+ desc: >-
+ Structured slash commands for AI coding assistants that guide you
+ through the complete integration lifecycle. Supports Claude Code,
+ Gemini CLI, and more.
+ - name: Wanaku
+ url: https://wanaku.ai
+ desc: >-
+ The Wanaku MCP Router is a router for AI-enabled applications
+ powered by the Model Context Protocol and Apache Camel.
+
+toolGroups:
+ - id: maven-plugins
+ title: Maven Plugins
+ intro: >-
+ For production projects, Camel provides a set of Maven plugins that
+ integrate with your existing build workflow.
+ items:
+ - name: Camel Maven Plugin
+ url: /manual/camel-maven-plugin.html
+ desc: "Run and develop Camel applications from Maven: camel:run,
camel:dev (hot-reload), camel:debug, camel:prepare-fatjar."
+ - name: Camel Report Maven Plugin
+ url: /manual/camel-report-maven-plugin.html
+ desc: Validates endpoint URIs, Simple expressions, duplicate route
IDs, and generates route coverage reports after unit testing.
+ - name: Camel YAML DSL Validator Maven Plugin
+ url: /manual/camel-yaml-dsl-validator-maven-plugin.html
+ desc: Validates YAML DSL route files for syntax errors according to
the spec, without needing to run Camel.
+ - name: Camel Component Maven Plugin
+ url: /manual/camel-component-maven-plugin.html
+ desc: Generates metadata and configuration Java classes for custom
Camel components.
+ - name: Camel REST DSL OpenAPI Plugin
+ url: /manual/rest-dsl-openapi.html
+ desc: Generates REST DSL routes and DTOs from OpenAPI v3 specification
files for a contract-first approach.
+
+ - id: archetypes
+ title: Maven Archetypes
+ intro: >-
+ Camel provides <a href="/manual/camel-maven-archetypes.html">Maven
+ Archetypes</a> to quickly scaffold new projects.
+ htmlIntro: true
+ mono: true
+ items:
+ - name: camel-archetype-java
+ desc: Creates a new Camel project using Java DSL
+ - name: camel-archetype-main
+ desc: Creates a new Camel project using standalone Camel Main
+ - name: camel-archetype-spring-boot
+ desc: Creates a new Camel project using Spring Boot
+ - name: camel-archetype-component
+ desc: Creates a new Camel component
+ - name: camel-archetype-dataformat
+ desc: Creates a new Camel data format
+ - name: camel-archetype-api-component
+ desc: Creates a new Camel component that wraps one or more API proxies
+
+ - id: ide
+ title: IDE Plugins and Extensions
+ items:
+ - name: Apache Camel IDEA Plugin
+ url: https://github.com/camel-tooling/camel-idea-plugin
+ desc: Camel editing capabilities for IntelliJ IDEA, including textual
route debugging.
+ - name: VS Code Extension Pack for Camel
+ url:
https://marketplace.visualstudio.com/items?itemName=redhat.apache-camel-extension-pack
+ desc: A set of VS Code extensions for developing Camel applications —
language support, debugging, and more.
+ - name: Camel Language Server
+ url: https://github.com/camel-tooling/camel-language-server
+ htmlDesc: true
+ desc: >-
+ LSP implementation providing completion, validation, hover, and
+ outline. Packaged for
+ <a
href="https://marketplace.visualstudio.com/items?itemName=redhat.vscode-apache-camel">VS
Code</a>
+ and
+ <a
href="https://marketplace.eclipse.org/content/language-support-apache-camel">Eclipse
Desktop</a>.
+ - name: Camel Debug Adapter
+ url: https://github.com/camel-tooling/camel-debug-adapter
+ htmlDesc: true
+ desc: >-
+ DAP implementation providing Camel textual route debugging.
+ Packaged for
+ <a
href="https://marketplace.visualstudio.com/items?itemName=redhat.vscode-debug-adapter-apache-camel">VS
Code</a>
+ and
+ <a
href="https://marketplace.eclipse.org/content/textual-debugging-apache-camel">Eclipse
Desktop</a>.
+
+ - id: visual
+ title: Visual Editing
+ items:
+ - name: Camel Karavan
+ url: https://karavan.space/
+ desc: A rich graphical editor for designing and deploying integration
routes.
+ - name: Kaoto
+ url: https://kaoto.io/
+ desc: >-
+ An integration editor to create and deploy workflows in a
+ visual, low-code way; with a code editor and deployments to the
+ cloud.
+
+ - id: monitoring
+ title: Monitoring and Management
+ items:
+ - name: Camel Monitor Operator
+ url:
https://camel-tooling.github.io/camel-dashboard/docs/installation-guide/advanced/operator/
+ desc: A Kubernetes operator that discovers and monitors Camel
applications, with a GUI dashboard and Prometheus integration.
+ - name: hawt.io
+ url: http://hawt.io
+ desc: An open source HTML5 web application for visualizing, managing
and tracing Camel routes & endpoints, ActiveMQ brokers, JMX, and more.
+ - name: Forage
+ url: https://kaotoio.github.io/forage/
+ desc: >-
+ Opinionated bean factories for Apache Camel — configure data
+ sources, connection factories, AI models, and more via
+ properties. Works with Camel JBang, Spring Boot, and Quarkus.
Review Comment:
Forage is now nested under “Monitoring and Management”, although its own
description identifies it as a bean-factory library and the previous page
placed it under “Libraries”. Restore a separate Libraries group so the rendered
tooling navigation and section classification are accurate.
##########
layouts/security/list.html:
##########
@@ -2,19 +2,49 @@
<div class="body">
<main>
- <article class="static doc security">
+ <article class="security">
- {{ .Content }}
+ <div class="security-hero">
+ <h1 class="page-hero-title">{{ .Title }}</h1>
+ <p class="page-hero-lead">{{ .Params.lead }}</p>
+ </div>
+
+ <div class="card-grid card-grid--2 security-grid">
+ <div class="card card--lg security-card--feature">
+ <div class="security-eyebrow">{{
.Params.read_first.eyebrow }}</div>
+ <h2>{{ .Params.read_first.title }}</h2>
+ {{ .Params.read_first.body | markdownify }}
+ </div>
+
+ <div class="card card--flat security-card">
+ <h3>{{ .Params.sbom.title }}</h3>
+ <p>{{ .Params.sbom.body | markdownify }}</p>
+ </div>
+
+ <div class="card card--flat security-card">
+ <h3>{{ .Params.policy_enforcement.title }}</h3>
+ {{ .Params.policy_enforcement.body | markdownify }}
+ </div>
+
+ <div class="security-band">
+ <div class="security-band-copy">
+ <h2>{{ .Params.reporting.title }}</h2>
+ {{ .Params.reporting.body | markdownify }}
+ </div>
+ <a class="button dark" href="{{ .Params.reporting.cta_url
}}">{{ .Params.reporting.cta_label }} →</a>
+ </div>
+ </div>
+
+ <h2 class="section-label">Security advisories</h2>
<div class="table-wrapper">
- <table class="tableblock frame-all grid-all stretch">
- <caption>Security advisories by year</caption>
+ <table class="security-advisories" aria-label="Security
advisories by year">
<thead>
<tr>
- <td>Reference</td>
- <td>Affected</td>
- <td>Fixed</td>
- <td>CVSS score</td>
- <td>Description</td>
+ <th>Reference</th>
+ <th>Affected</th>
+ <th>Fixed</th>
+ <th>CVSS</th>
Review Comment:
This column renders categorical values such as `CRITICAL`, `HIGH`, and
`MEDIUM`, not CVSS numeric scores. Labeling it “CVSS” misrepresents the
advisory data; call it “Severity” unless actual CVSS scores are added.
##########
layouts/partials/releases/downloads.html:
##########
@@ -144,37 +134,6 @@ <h2 id="{{ $.Category.id }}"><a class="anchor" href="#{{
$.Category.id }}"></a>{
{{ end }}
<tr>
Review Comment:
After removing the Version and Note columns, this table has two columns, but
the no-path download branch still emits `colspan="3"` below. Camel Kafka
Connector has a `Binaries` entry without `path_format`, so its release pages
will render an extra phantom column; update that fallback span to two.
##########
data/chrome.yaml:
##########
@@ -0,0 +1,61 @@
+# Shared site chrome. Read by Hugo as .Site.Data.chrome and by the Antora UI
+# through src/helpers/withChromeData.js. Edit here, never in the templates.
+brand:
+ name: Apache Camel
+ blurb: >-
+ Open source integration framework. An Apache Software Foundation project,
+ available under the Apache v2 license.
+
+columns:
+ - title: Overview
+ id: overview
+ links:
+ - { name: Blog, url: /blog/ }
+ - { name: Documentation, url: /docs/ }
+ - { name: Tooling, url: /tooling/ }
+ - { name: Community, url: /community/support/ }
Review Comment:
The new `/community/` landing page is the destination used by the main
navigation, but this shared footer link still bypasses it and opens the Support
subpage. Point “Community” at the redesigned landing page so both Hugo and
Antora footers expose it.
##########
static/.htaccess:
##########
@@ -878,11 +878,12 @@ Redirect 301 /polling-consumer.html
/components/next/eips/polling-consumer.html
Redirect 301 /predicate.html /manual/predicate.html
Redirect 301 /processor.html /manual/processor.html
Redirect 301 /producertemplate.html /manual/producertemplate.html
-Redirect 301 /projects/ /docs/
-Redirect 301 /projects/camel-k /docs/#apache-camel-k
-Redirect 301 /projects/camel-quarkus /docs/#apache-camel-extensions-for-quarkus
-Redirect 301 /projects/camel-kafka-connector
/docs/#apache-camel-kafka-connector
+Redirect 301 /projects/camel-k /projects/
+Redirect 301 /projects/camel-quarkus /projects/
+Redirect 301 /projects/camel-kafka-connector /projects/
Review Comment:
`Redirect` performs prefix matching, so the first rule also catches
`/projects/camel-kafka-connector` and appends `afka-connector` to the target;
slash-suffixed requests similarly become `/projects//`. Anchor these aliases
(and add redirect tests for all three aliases with and without a trailing
slash) so every legacy URL lands on `/projects/`.
--
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]