aashnajena commented on pull request #370:
URL: https://github.com/apache/camel-website/pull/370#issuecomment-638946145


   > I think this change bites more than it needs to, I would make it much 
simpler for the first iteration.
   > 
   > I have concerns about introducing new design elements without 
incorporating them with the rest of the website, e.g. looking at the difference 
between the way similarly purposed design is presented on the frontpage and on 
the projects page links that look like buttons are very much different than the 
current design; underlining the headings for project names; abbreviating 
"Documentation" to "Docs"; having a border around project cards.
   > 
   > I think we should consolidate the design across the frontpage and the 
projects page.
   
   Okay, I understand. Here's what I think we can do :
   1) Make the CSS as much common as possible for front page projects section 
and projects page. We can include the border on the front page and remove the 
underlined headings on the projects page (although this is the default 
behaviour of H2 on the rest of the website)
   2) We can either remove the button-shaped links on the projects page and 
make them similar to the frontpage : eg ``` option1 | option2 | option3 ```  or 
we could adapt the frontpage - have just the icons for each project card, 
because the buttons with icons+text would be too big.
   3) As for the abbreviations, documentation -> docs was done to reduce the 
length. I agree, on the menu and the front page, we have used the term 
"documentation", but I feel that "docs" is quite an accepted abbreviation and 
earlier we used to have a "read the docs" button on the front page. I'm not 
sure about this issue though, please tell me what to do here. As mentioned in 
(2), we can replicate the way links are presented on the front page. 


----------------------------------------------------------------
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:
us...@infra.apache.org


Reply via email to