jbertram commented on pull request #58: URL: https://github.com/apache/activemq-website/pull/58#issuecomment-909839143
> We can't use a web framework, such as Jekyll, and simultaneously not use it. I apologize if my comment communicated this logical fallacy. I'm not saying we shouldn't use Jekyll. Clearly we are _already_ doing that. My point was simply that we should be circumspect in _how_ we use it, especially with more advanced features. If this specific change is really as simple as it's made out to be then I don't see a problem with regard to the new complexity. Still, the point is worth making to ensure we cover our bases especially given our unique context (i.e. a clear history of poor website maintenance). Might I suggest something like the following?  Noteworthy changes: - "News" top-level menu item - Main banner height slightly reduced to bring subsequent items up a bit - Very clear and succinct bulleted list of most recent news items in chronological order - Decreasing clutter tends to increase readability therefore... - Items are simple links which can be followed for more details - Redundant "Read More" button is eliminated - The list is not immediately after the banner, but is still clearly displayed without scrolling; I felt this was a good compromise as I would personally prefer it be even further down - A bit cleaner visual separation from the surrounding text items Regardless of the visual design I agree with Robbie that linking to old releases from the main page should be avoided. I also don't like the page-per-release. I think that each component should have a "latest" page and a "past releases" page and that's it. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
