I think you could probably improve the usefulness and ease of use (and therefore success) of this project with a little extra leg work. First, add an additiona

I think you could probably improve the usefulness and ease of use (and therefore success) of this project with a little extra leg work. First, add an additional requirement to contributing--require each sub folder to the project contain a manifest (json format) that describes some key information about the contribution: [{ author: 'giberson', name: 'pixel button', descripton: 'classic pixel outlined button', template: pbutton.html, stylesheet: 'pbutton.css', type: 'layout|widget', version: 1 }] Second, actually build a site similar in functionality to Google's font site, the content generated by parsing the main trunk contribution folders. (see http://www.google.com/webfonts http://www.google.com/webfonts) This way users can browse the contributed content with inline examples. You can also provide the user with a "quick use" button that produces the stylesheet href link, and the html code to insert into their page to use the style. Notes on the manifest entries: The main object of the manifest is an array, allowing for multiple components to be housed in a single contribution folder. "template" is the html markup to be styled via css. "stylesheet" is the stylesheet to be included by the page. "type" is either layout or widget to represent if the styling/template are meant to replace your html or be inserted into it. Which will help the directory site determine best method to display preview, via an inline div or a popup div or some other creative mechanism. "version" represents the manifest version, it allows you to upgrade the site and filter out contributions that have been updated with new required/optional manifest field properties or formats to work with new site features.