Yes, the initial design says: "I am boring bunch of links from people broken by routine" ;-)
It could Use ART, some clever animation (remember this? http://devthought.com/2007/01/29/cssjavascript-true-power-fancy-menu/), something people would instantly want to use on their sites. Reference page with links could be one step deeper. Thanks, On Sep 17, 5:46 pm, Eli <[email protected]> wrote: > My two cents: > The site has no "Hey! This is a JAVASCRIPT FRAMEWORK FOR DOING THIS > AND THAT". > It starts off with "demos" guides and api reference right off the bat, > and it needs a little more "newbie" friendliness. > > There are a few worse sites than those don't don't explain their > purpose from the second you look at them. > > Answer those questions as a start: > What is this? > Who is it for? > Why this and not that (jquery/prototype)? - maybe a short differences > table > What do I need to start? (you've got jsfiddle = nothing but a good > browser) > Where to go from here? > > Keep the existing links as well, but don't make them the main theme. > > -Eli > > On Sep 16, 9:46 pm, fakedarren <[email protected]> wrote: > > > > > > > > > Hi everyone > > > We've started work on a new site for MooTools, and wondered if any of you > > wanted to help out. The is a lot of work to be done, requiring a variety of > > skills: > > > - Design > > - HTML & CSS > > - Wordpress customisation > > - 'Classic' PHP (for the bulk of the site and the documentation / demo > > runner) > > - Symfony (for the Forge) > > - Content contributions - tutorials, demos, documentation > > > We've already sketched out some initial design ideas <http://d.pr/uxWg> and > > the first stage is to flesh out the 'style > > guide<https://github.com/fakedarren/mootools-website/blob/master/DESIGN%20A...>' > > - covering basics, like heading styles, paragraph and link styles, code > > snippet styles - so that when we move on to specific sections, anyone that > > wants to help with design knows where to start. > > > So how do you get involved? Well, we have a Github > > repository<https://github.com/fakedarren/mootools-website>and all you need > > to help out is going to be put there. 'Watch' the > > repository to get notified of any issues, and you can comment with any > > questions or ideas. > > > Don't know git? That is fine, if you want to contribute designs only, you > > can submit design ideas by email (fakedarren at mootools dot net) but you'll > > need to create a (free!) account to take part in any discussions. If you > > want to contribute code, you will need to use git. > > > So - what is it we want you to do? > > > Well, we have a list of milestones / > > steps<https://github.com/fakedarren/mootools-website/issues/milestones>, > > and within each step, a list of > > tasks<https://github.com/fakedarren/mootools-website/issues?milestone=1>. > > Each milestone should take approximately two weeks to complete. We'll log > > tasks accordingly. If it's not assigned to anyone, it is still outstanding, > > and any contributions are more than welcome. > > > For now, we're still waiting on real basics - a basic style guide, a colour > > palette, the main navigation - if you want to get involved, please do. > > > A massive part of the new website is to beef up our 'learning' section - so > > if you want to help with content, take a look at the Tutorials section, and > > see if there is anything you can help with. > > > If there is anything you feel the new website should have, please create a > > new issue, and it will be discussed. > > > Cheers > > Darren
