[ https://issues.apache.org/jira/browse/CAMEL-14910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116913#comment-17116913 ]
David Jencks commented on CAMEL-14910: -------------------------------------- This issue is closed, lets discuss on the PR. > Decide if component summary pages are a good idea > ------------------------------------------------- > > Key: CAMEL-14910 > URL: https://issues.apache.org/jira/browse/CAMEL-14910 > Project: Camel > Issue Type: Improvement > Components: website > Affects Versions: 3.2.0 > Reporter: David Jencks > Priority: Major > Attachments: aws2.png, getting-started.png > > > I discovered some component summary pages while working on CAMEL-14874 > and included them in the nav pane and index table. Claus suggested that the > Spring one was useful and the others should be dropped. The Kubernetes > summary page is heavily linked back and forth to the individual Kubernetes > components. > > In general, due to the extremely long components list, I'm inclined to think > that any possible kind of grouping is a good idea. If there are going to be > summary pages, then they should all be similar in some way. > * Should there be summary pages for groups of related components? > * What should their structure and appearance be? > * Should the nav pane indent the components in a group? -- This message was sent by Atlassian Jira (v8.3.4#803005)