djencks commented on issue #692: URL: https://github.com/apache/camel-website/issues/692#issuecomment-981114548
I don't see the principles behind your suggested ordering. Here are my thoughts: user manual -explains what camel is all about, needs to be first camel - camel core, needs to be next, everything else depends on it. ... kamelets - IIUC this is a generic way of representing partial configurations of one or more camel components, usable in several environments. This is qualitatively different from everything else, and it makes sense to me to put it at the end. ---- Everything else.... IIUC these are ways of running camel components in different environments, with various degrees of generated and hand-written wrapper code. I can think of two reasonable orderings: - alphabetical, yielding what we have now except with kamelets at the end. - by increasing amount of generated and hand-written wrapper code. I'm not sure but I think this would yield something like Camel-Karaf Camel-Spring-Boot Camel-K Camel-Kafka-Connector Camel-Quarkus How did you select the ordering of these items? -- 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: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
