[ 
https://issues.apache.org/jira/browse/WICKET-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236716#comment-14236716
 ] 

Martijn Dashorst commented on WICKET-3341:
------------------------------------------

While I appreciate the work that went into it, I am seriously against any 
carousel, and this one in particular because it doesn't make the design better, 
it makes it worse. There are several reasons why I want to kill it before it 
hits apache.org

- my design does not feature one. I deliberately did not add a carousel.
- my graphics are unsuited for being part of the carousel: they are fuzzy, 
under-designed, have too little detail, are crude
- hence it makes the site look amateurish
- the carousel doesn't add anything to the page other than some movement
- thus I have to wait some indeterminate time or click on buttons for new 
content 
- the content is just bland: it is just a heading without any context or 
content.
- Carousels are inherently awful for accessibility. They require javascript, 
change content on a whim and don't add value for non-visual browsers.

This is not how I designed the page. I deliberately didn't design a carousel in 
the pages. I did it once for an earlier concept showing sites that use Wicket, 
but I didn't like it. Reading up on carousels further cemented my opinion that 
they are evil and should be banned.

I want our front page to be deliberate, to have an air of maturity, to strive 
to be non-buzzwordy. If we claim something I want us to back it up. Anyone can 
say "We're secure by default"–we can back it up. If I see a website with just 
the claim and nothing to back it up I assume it is just doing lip service and a 
marketing person wrote it up because they saw it on another web site.

> 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)

Reply via email to