Hi Yeah I agree that those top part of the components pages should be linking to spring boot, quarkus or kafka connector (and maybe also karaf) for the supported runtimes. Maybe there was summary in the bottom that listed which runtimes it supported and link to those pages.
Another idea would be for the users to select runtime, eg "sprint boot" and the website "adapts" to this choice. On Thu, Sep 24, 2020 at 10:15 PM Peter Palaga <ppal...@redhat.com> wrote: > > Hi, > > as pre-discussed with some of you, we'd like to add links from component > pages (such as > https://camel.apache.org/components/latest/activemq-component.html ) to > the Camel Quarkus extension page providing support for the given > component (such as > https://camel.apache.org/camel-quarkus/latest/reference/extensions/activemq.html > ) > > Technically, we can leverage the Camel Quarkus metadata included in the > component pages since this recent PR: > https://github.com/apache/camel/pull/4288/files (Thanks David Jencks for > helping with that!) We can write an ad hoc AsciiDoc extension that adds > links based on that metadata. I'd work on this unless somebody has a > better idea? > > While I have some technical vision, I am not sure at all, where to put > the links in the current layout and what they should look like. I'd be > thankful for any suggestions. > > The current layout of the component pages is a bit Spring Boot centric > and I wonder whether we should make it more platform neutral, where all > supported platforms (SB, Karaf and Quarkus) are listed in a visually > balanced way? > > Thanks, > > -- Peter > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
