I’ve been studying the camel-quarkus website wondering about generating the table of extensions and I have some questions….
The page is named “list of extensions” but that’s not what it actually is. It has tables of components, data formats, and languages, with links to the extension they are in. I find this confusing. What are users likely to find most useful? Are they likely to think of the components, data formats, and languages they need and want to know what extensions are needed to run in camel-quarkus? Or are they going to search directly for extensions? Or both? If it’s the former, I think having separate index pages for the types of “thing” would be a good idea, to match the main camel website. Then there’s the question of what you get to when you select a “thing”. The extension pages don’t seem to me to be a very good match for clicking on a “thing” in an extension. I think it would make more sense to show a wrapper around most of the main camel “thing” page, the wrapper indicating something about the extension that provides the “thing”. Leaving out the information not useful for camel-quarks would be a good idea too… I think this includes the “main” camel maven coordinates. As part of this question, is Spring Boot relevant to camel-quarkus? On the other hand, if users are more likely to be looking for extensions directly, then actually having a table of extensions would be a good idea. The list of extensions could also show up in the nav as a collapsible level 2 list. Furthermore, would it be good to have links from the main camel “thing” pages to the quarkus extension providing them? thanks David Jencks
