I really like this idea, and it's one I wish I had time to work on myself. I think there's a real need for something like this. I've come to the conclusion tha

I really like this idea, and it's one I wish I had time to work on myself. I think there's a real need for something like this. I've come to the conclusion that a project like this would only be successful if contributors are expected to document WHY the code used is written as it is. Without documentation (an example UI style guide, like the homepage of Twitter Bootstrap) it's difficult to see both the big picture and the purpose of the small details. Twitter Bootstrap had a great home page right from the start – it served as documentation for the project, as well as a marketing demo influencing you to try it. So imagine if the contributors to your repo were simply asked to follow a few guidelines, documenting their contributions (say, providing example HTML and using KSS to markup their CSS). https://github.com/kneath/kss https://github.com/kneath/kss http://www.alistapart.com/articles/writingainterfacestyleguide/ http://www.alistapart.com/articles/writingainterfacestylegui... http://www.engineyard.com/blog/2011/front-end-maintainability-with-sass-and-style-guides/ http://www.engineyard.com/blog/2011/front-end-maintainabilit... Maybe ask them to follow a few of the "Object Oriented CSS" principles, so that it's easier to mix and match parts from different folders: https://github.com/stubbornella/oocss/wiki https://github.com/stubbornella/oocss/wiki Principles of separating the "structure" from the skin"; and separating "container" from "content".