[
https://issues.apache.org/jira/browse/CAMEL-14907?focusedWorklogId=423119&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-423119
]
ASF GitHub Bot logged work on CAMEL-14907:
------------------------------------------
Author: ASF GitHub Bot
Created on: 15/Apr/20 22:35
Start Date: 15/Apr/20 22:35
Worklog Time Spent: 10m
Work Description: djencks commented on pull request #3751: Fixes
CAMEL-14907: separate core and non core components in index page tables
URL: https://github.com/apache/camel/pull/3751
----------------------------------------------------------------
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.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 423119)
Time Spent: 20m (was: 10m)
> Consider separating core and non-core components in the components index page
> -----------------------------------------------------------------------------
>
> Key: CAMEL-14907
> URL: https://issues.apache.org/jira/browse/CAMEL-14907
> Project: Camel
> Issue Type: Improvement
> Components: website
> Affects Versions: 3.2.0
> Reporter: David Jencks
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The user manual index page list of components (which should not be there, see
> https://issues.apache.org/jira/browse/CAMEL-14906) separates core and
> non-core components. Should the components index page and/or the components
> nav pane also separate them in this way? The index page would be easy to do,
> I'd rather wait on the nav pane until the nav list can be generated in the
> same way as the table.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
