You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <da...@apache.org> on 2026/10/21 10:51:58 UTC
Vote: new website styling for Wicket 11 and beyond
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
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Martin Grigorov <mg...@apache.org>.
+1 for D
Thank you, Martijn!
Martin
On Wed, Oct 21, 2026 at 1:52 PM Martijn Dashorst <da...@apache.org>
wrote:
> 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
>
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Pedro Santos <pe...@gmail.com>.
C, D, A
Pedro Santos
Em qua., 21 de out. de 2026 às 11:36, Martijn Dashorst <
martijn.dashorst@gmail.com> escreveu:
> Oh FYI: on the ribbon, the season selector will be invisible for normal
> use. I added it to show what will happen in different seasons.
>
> Martijn
>
>
> Become a Wicket expert, learn from the best: http://wicketinaction.com
>
> On Wed, 21 Oct 2026 at 14:44, Emond Papegaaij <em...@gmail.com>
> wrote:
>
> > My vote: C, B
> >
> > Emond
> >
> > Op wo 21 okt 2026 om 13:44 schreef Daniel Bartl <me...@danielbartl.com>:
> >
> > > Hi Martijn,
> > >
> > > many thanks for your time and effort!
> > >
> > > My vote: C, B, D.
> > >
> > > Daniel
> > >
> > > On Wed, Oct 21, 2026, at 12:51 PM, Martijn Dashorst wrote:
> > > > 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
> > > >
> >
>
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Martijn Dashorst <ma...@gmail.com>.
Oh FYI: on the ribbon, the season selector will be invisible for normal
use. I added it to show what will happen in different seasons.
Martijn
Become a Wicket expert, learn from the best: http://wicketinaction.com
On Wed, 21 Oct 2026 at 14:44, Emond Papegaaij <em...@gmail.com>
wrote:
> My vote: C, B
>
> Emond
>
> Op wo 21 okt 2026 om 13:44 schreef Daniel Bartl <me...@danielbartl.com>:
>
> > Hi Martijn,
> >
> > many thanks for your time and effort!
> >
> > My vote: C, B, D.
> >
> > Daniel
> >
> > On Wed, Oct 21, 2026, at 12:51 PM, Martijn Dashorst wrote:
> > > 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
> > >
>
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Emond Papegaaij <em...@gmail.com>.
My vote: C, B
Emond
Op wo 21 okt 2026 om 13:44 schreef Daniel Bartl <me...@danielbartl.com>:
> Hi Martijn,
>
> many thanks for your time and effort!
>
> My vote: C, B, D.
>
> Daniel
>
> On Wed, Oct 21, 2026, at 12:51 PM, Martijn Dashorst wrote:
> > 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
> >
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Daniel Bartl <me...@danielbartl.com>.
Hi Martijn,
many thanks for your time and effort!
My vote: C, B, D.
Daniel
On Wed, Oct 21, 2026, at 12:51 PM, Martijn Dashorst wrote:
> 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
>
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Maxim Solodovnik <so...@gmail.com>.
Hello All,
D, A
On Thu, 22 Oct 2026 at 12:44, Korbinian Bachl via dev
<de...@wicket.apache.org> wrote:
>
> My picks: D, A, C
>
> ----- Ursprüngliche Mail -----
> > Von: "Martijn Dashorst" <da...@apache.org>
> > An: "dev" <de...@wicket.apache.org>
> > Gesendet: Mittwoch, 21. Oktober 2026 12:51:58
> > Betreff: Vote: new website styling for Wicket 11 and beyond
>
> > 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
--
Best regards,
Maxim
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Korbinian Bachl via dev <de...@wicket.apache.org>.
My picks: D, A, C
----- Ursprüngliche Mail -----
> Von: "Martijn Dashorst" <da...@apache.org>
> An: "dev" <de...@wicket.apache.org>
> Gesendet: Mittwoch, 21. Oktober 2026 12:51:58
> Betreff: Vote: new website styling for Wicket 11 and beyond
> 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
Re: Vote: new website styling for Wicket 11 and beyond
Posted by Matt Pavlovich <ma...@apache.org>.
These are great! Especially enjoy the pages that show how to code a Wicket page in steps. Super user-friendly!
My picks: D, A, C
> On Oct 21, 2026, at 5:51 AM, Martijn Dashorst <da...@apache.org> wrote:
>
> 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