gemmellr edited a comment on pull request #58: URL: https://github.com/apache/activemq-website/pull/58#issuecomment-910296630
The thing I am absolutely against is having prominent entries on the front page as 'news', linking through to specific old release pages with non-mirrored downloads for the stale/old release. We should direct folks to the download page that has the latest release and if they are determined on using old non-mirrored ones they can find it easily from there given we link to the old releases page. If we do that, then I would say having old release entries on would be far less of an issue, even though I still really dont think stale release entries should be there at all, especially instead of e.g putting continued focus on another still-current release of some other component, or a CVE notice, or really anything else considered news worthy enough to be there. I probably prefer the horizontal approach, and think its nice being above the blurb but only if much much smaller. I do like the single-line entry size in Justins alternative idea (but would include the date), and especially getting rid of the 'Read More' button and all the space used by just making the entry title be the actual link. Anything done should perhaps have a small link to the actual full news page if there is to be one (again perhaps just using the title would do). E.g for me something simple like a single line running across with the link and date would be nicer, i.e: >\<Heading Banner\> >News: ActiveMQ Bar X.Y.0 (Sept 3, 2021) | ActiveMQ Foo X.Y.1 (Sept 2, 2021) | ActiveMQ Foo X.Y.0 (Sept 1, 2021) > \<Main Blurb\> Its still going to be very prominent just because of where it is and it being the first content of meaning on the page. It doesnt need to take up like 20% of the visible space on a screen. -- 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]
