Hi,
We currently have manually curated per-Camel-Quarkus-extension pages
rather rarely, esp. when there is some additional config option or
important difference between the given Camel Quarkus extension and the
underlying Camel component. Here are some examples:
* https://camel.apache.org/camel-quarkus/latest/extensions/ahc.html
* https://camel.apache.org/camel-quarkus/latest/extensions/couchdb.html
* https://camel.apache.org/camel-quarkus/latest/extensions/dozer.html
* https://camel.apache.org/camel-quarkus/latest/extensions/fhir.html
* https://camel.apache.org/camel-quarkus/latest/extensions/graphql.html
Are separate Camel Quarkus pages actually the best way to document
additional config options, important differences against vanilla Camel
and showing the Maven coordinates for the given extension?
Luca pointed out today that Spring Boot starter info is listed directly
in the Camel component pages and that Camel Quarkus info should probably
go there too.
I must say I find the component pages long enough already. I am not sure
bloating them even more with the Camel Quarkus stuff would bring enough
value to the users. Does actually anybody think this would be the way to go?
Per-extension pages are handy for one more reason: Quarkus metadata for
http://code.quarkus.io/ requires a link that is used there to open "a
guide" for the given extension.
We currently use https://quarkus.io/guides/camel for all our extensions.
That's far from being user friendly. Having a page for each Camel
Quarkus extension would be much better I think.
I'd appreciate any feedback.
Thanks,
-- Peter
