jbertram commented on pull request #58: URL: https://github.com/apache/activemq-website/pull/58#issuecomment-909373769
> Plus the 'number of bugs/etc' summary complicates the steps needed to add a release to the site. Although I do see value in having this summary, I think this is a compelling point. The less manual work needed for a release the better. > The news feed reflects the community activity. So is the underlying goal here really just to help users quickly and easily see that there's activity within ActiveMQ? If so, is there a specific reason why this is a concern? Are users coming to you and asking if ActiveMQ is still active (no pun intended) or is this just a proactive step you think the project should take? Please elaborate. For what it's worth, there are lots of ways to see project activity (e.g. Jira, GitHub commits, mailing lists, etc.) all of which are linked to from the website and readily accessible to interested parties. > There is always a ton of activity around ActiveMQ, but the project page is very stagnant. *Stagnant* is a bit pejorative, but from a design perspective I actually quite like a mostly static main page as I think it's good for usability. It certainly helps returning users who expect key touch points and information to be in the same place as before. Currently the main page clearly states the purpose of the project, what platforms it supports, what protocols it supports, some basic use-cases, etc. All this information is especially important to new users. It's not clear to me that a demonstration of recent activity deserves to be more "front and center" than this. I have no issue with a new top-level menu item called "News" (or whatever) that would have the content you're suggesting. I think such a page would follow a pretty well-established web paradigm. I also have no issue with some kind of "Latest News" widget on the main page with the 3 most recent news items, but I think it shouldn't take such a prominent position. Given the not-so-distant past of the website with all the broken links, out-dated/irrelevant/repeated information, etc. I'm loathe to add much complexity. The simpler the website is the easier it will be to update (and potentially migrate) in the future. The deeper we get into Jekyll features the more work it will be to get out eventually. By this I don't mean we shouldn't have a news page; I just think we should proceed with caution to avoid repeating previous mistakes. -- 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]
