1,261 karma · joined November 1, 2012
Right now we're only using it for our upcoming signup/login redesign, but it's available for use elsewhere and will probably start popping up on other interaces. We debated whether to even include the Sass files and associated errata at all though, to be honest.
Anybody else a little depressed that Google employees took precedent in this story, over an _ultrasound center_ housed on a site with chemicals that might cause birth defects?
It is a fairly common pattern in nav menus to have an indicator -- the unread count or down arrow in this case -- at the top level, but not at the second or third level, and instead rely on simply hovering on the submenu to open the next level.
"there's no visual cues to let me know the buttons are clickable until I am already interacting with them"
Except one of the most powerful cues, action verbs in button copy. You could easily make the same claim you just made about say, menu item styles in OSX. The reason why the buttons seem so bad in this case is in part because it's just a demo with a wall of buttons.
Where I agree with people critical of flat designs, such as what Nielsen says, is that it breaks down in anything with anything particular complicated or with many menus and actions. That clutter of meaningless buttons at the top of the demo is a good example. But for cases where you have a simple design that can be driven by color and typography, it can work. Have a little imagination. There is no 100% good or bad trend in design. Just different solutions for different problems.
We're the experimental features team at the Wikimedia Foundation, the nonprofit that supports Wikipedia and other free knowledge projects.
We're looking for full stack engineers, ideally with a bent towards frontend work, that can help us fix the experience of editing Wikipedia. Wikipedia has ~450 million monthly unique visitors, but only about 80,000 monthly contributors, and that enormous disparity is what we're working to correct.
Rather than describe all aspects of what we're doing, here's a blog post describing one of the projects on our plate, and how it relates to our general approach:
http://blog.wikimedia.org/2012/10/24/fix-this-broken-workflo...
The post also includes links to apply, and some examples of what we've done in the past.