[
https://issues.apache.org/jira/browse/WICKET-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14234169#comment-14234169
]
Martijn Dashorst commented on WICKET-3341:
------------------------------------------
Carousels are an anti pattern: to quote from an interview
(http://www.creativebloq.com/accessibility-expert-warns-stop-using-carousels-7133778):
> Carousels are seemingly an easy fix to two universal design problems: how do
> I fit
> so much content into so little space, and how do I decide what content is the
> most
> important? It's easy to justify away the usability issues of a carousel when
> you
> consider the benefits of presenting multiple content pieces in such little
> real estate.
> This has been exacerbated by unfounded focus on above-the-fold design.
They are a cop-out: you can't decide what is the most important, so everything
is important. And you hide (N-1)/N of the important stuff behind a wait until
you see it (or you have to click through the list).
It doesn't give a fast overview of something because it hides (N-1/N) of the
content all the time.
Why *do* you want a carousel? Because it is pretty? Because everybody has one?
Because Bootstrap provides one? What do you want to achieve with the carousel?
Why can't that goal not be attained with just plain visible content?
As for Github: why not bitbucket, source forge, google code, and any other
provider of git repositories? Why single out github on such a prominent place?
They are not sponsors of the ASF, and the ASF even has less screen real estate.
We are an ASF community after all, so we should be touting that instead of a
direct link to a commercial entity's website.
I like github, but I don't think it is the goal of and in the best interest of
Wicket to promote github.
> New design for wicket site
> --------------------------
>
> Key: WICKET-3341
> URL: https://issues.apache.org/jira/browse/WICKET-3341
> Project: Wicket
> Issue Type: Improvement
> Components: site
> Reporter: Martijn Dashorst
> Attachments: ASF.LICENSE.NOT.GRANTED--Alternative design.jpg,
> Keynote001.png, KeynoteScreenSnapz001.png, KeynoteScreenSnapz002.png,
> KeynoteScreenSnapz003.png, KeynoteScreenSnapz004.png,
> KeynoteScreenSnapz005.png, logo.wicket.ai, logo.wicket.jpg,
> wicket-flat-new-top.002.png, wicket-flat-new-top.003.png,
> wicket-flat-new-top.004.png, wicket-flat-new-top.005.png,
> wicket-flat.001.png, wicket-logo-big.png, wicket-logo.svg
>
>
> Our current site design has been with us for quite a while. It looked fresh
> in the 1980s, but now it has gone stale.
> This is a proposal for a new, fresh design of the home page and sub pages.
> The home page will feature a prominent download link, a list of feature
> descriptions, screenshots of sites powered by Wicket, official blog items and
> Buzz by our users.
> The screenshots of wicket powered websites will link to short descriptions of
> the sites under /meet/poweredby. Links to the websites will of course have
> nofollow
> Other pages will feature a menu on the right side of the page providing
> direct links to content.
> Attached are a couple of screen shots of how the site might look like.
> Screen 005 is an alternative of the home page without the list of features,
> but including the introduction to wicket article.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
