You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2020/07/20 18:17:54 UTC
[GitHub] [camel-website] AemieJ commented on pull request #432: CAMEL 15296: Create sitemap for Camel website
AemieJ commented on pull request #432:
URL: https://github.com/apache/camel-website/pull/432#issuecomment-661253471
This is just a basic draft on the creation of a sitemap so I have suggestions regarding designs and not design-related as well.
1. Within the Camel Website sitemap, The blog is displayed after the releases. So either we include all of the camel releases or we just included the releases within the blog category. I don't see the reason to include both of them. It's redundant.
Another is within the community where support is included twice. This is only 'cause both Mailing Lists and Getting Help tends to have the same title. So @zregvart is it best to call the mailing list as the title instead of having support as the title followed by mailing lists. I would like to know your opinions on this one.
Within apache camel security, it's best to just include the `CVE-` part only.
2. For the user manual sitemap, I was thinking to include FAQ as a separate module of the sitemap itself. In addition to it, we don't require the Components, EIP within the user manual sitemap, it's good to remove the ones that are related to the camel components section.
3. I like the detailing of the component sitemap listing but we will have to think of a manner in which we present the layout. If the above two non-design related issues are handled, I would also like the columns to be in a count of 3, covers less vertical space.
An idea on how I want the normal list to be presented is in the image below. For the components, I will need to give a look into that.
----------------------------------------------------------------
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:
users@infra.apache.org