Uploaded image for project: 'Camel'
  1. Camel
  2. CAMEL-14910

Decide if component summary pages are a good idea

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.2.0
    • Fix Version/s: None
    • Component/s: website
    • Labels:
      None
    • Estimated Complexity:
      Unknown

      Description

      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?

        Attachments

        1. aws2.png
          48 kB
          Aemie
        2. getting-started.png
          9 kB
          Aemie

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              djencks David Jencks
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: