You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Aemie (Jira)" <ji...@apache.org> on 2020/05/26 06:14:00 UTC
[jira] [Commented] (CAMEL-14910) Decide if component summary pages
are a good idea
[ https://issues.apache.org/jira/browse/CAMEL-14910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116471#comment-17116471 ]
Aemie commented on CAMEL-14910:
-------------------------------
I have observed that there are various related components including AWS2, AWS, Hazelnut, Spring, and various others as well & listing all on the nav panel creates messiness, entropy & redundancy. However, I also observed that are few components including Hazelnut that describe the summary of its related component. Hence, I thought we could achieve this by bundling all related components in their parent unit as shown below and the indentation would be similar to as shown in the example.
!getting-started.png|width=159,height=72! We could perform the bundling as similar to this.
All the AWS related components listed as it creates high entropy and makes searching for a user quite heavy job.
!aws2.png!
> 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)