TL;DR: there's a vote at the end of this message. I have done considerable work on what I think is a significant improvement over the old site. This restructure is now live on https://wicket.apache.org, but I want the site to go further.
First what is already achieved, I have restructured the site to: - have fewer top level menu items - give the blog more prominence - have community capture both support and contribute - give ASF and a link to our Github repo prominence (not that we value GH over ASF, but we don't want people /have/ to look for the link) - have documentation according to Diataxis (How-to's, Tutorials, Explainers and References) - have search to our documentation, including a glossary, index, and more - give each release line (wicket-10.x, wicket-9.x, wicket-8.x, etc) their own page - update the blog to be categorized with each release line, and also featured posts - give every release line page the facts you look for: its status, the date support ends, the Maven dependency with a copy button, requirements, downloads and how to upgrade to the next line - use one vocabulary for release status everywhere: LTS, Current and end of life, instead of "for production" and "for new features" - put the newest release in the menu, leading to its line's page - bring back the quick start wizard, under Releases - link the reference guide (one page and PDF) and the Javadoc of every release line from the documentation - write the guide as about 140 pages by topic and kind, each marked with the Wicket version it applies to - teach the search the release vocabulary, so "LTS" or "10" finds the right page - put questions, bug reports, reporting a vulnerability and the mailing lists on one Community page - sort the contributor documentation by kind under /contribute/ - give long pages an "On this page" rail beside the text - give the homepage a Get started button, the release lines in the hero, the featured blog posts right below it, a page shown as its Java and its HTML, and the newest Built with Wicket showcases - make the release tables and the homepage work on phones - add a site footer, a 404 page that helps you on your way, and an llms.txt for AI assistants What's next: On top of the new structure I made three new designs, to make the site fresher and more modern. Each has an introduction on the homepage that shows how Wicket works; Ribbon also has a separate page that builds one page in seven steps, which I intend to extend to explain more concepts visually: https://dashorst.github.io/wicket-site/ribbon-site/start/overview.html The previews show the content as it will be on release day (11.0.0 and 10.12.0 out), so some dates are in the future. These are the choices: A - Current: https://dashorst.github.io/wicket-site/structure/ B - Departure board: https://dashorst.github.io/wicket-site/departure-board/ C - Reveal: https://dashorst.github.io/wicket-site/reveal-site/ D - Ribbon: https://dashorst.github.io/wicket-site/ribbon-site/ E - Other, ... Please rank the choices in order of preference, most preferred first, for example "D, B, A". You don't have to rank every choice. If you choose E, say what you have in mind. Everyone is welcome to vote, and in the case of a split decision, the PMC votes will be binding. The vote runs for at least 72 hours. I'll count it as an instant runoff: the choice with the fewest first preferences drops out and its votes go to their next choice, until one choice has a majority. Onwards to Wicket 11 and beyond! Check the proposals and give us your preference(s)! Martijn
