kss

(Maintainer of KSS here) A point of clarification, the inclusion of HTML in KSS blocks is actually a pattern I actively recommend against. It's something I've chosen not to include in KSS core a number of times for exactly this reason (even when my own co-workers submit the PR: https://github.com/kneath/kss/pull/97) If you're using KSS, I highly recommend tying it as close to your actual markup generation as possible. For me, that means rendering partials directly from rails with dummy objects. That way if the partial changes, the styleguide changes.

I made StyleDocco (http://jacobrask.github.com/styledocco/) for this purpose. You add example HTML (and Markdown) in your stylesheets, and StyleDocco generates documentation files with the rendered HTML as well as the HTML code snippets. There's also Knyle Style Sheets (https://github.com/kneath/kss) if you like a more structured TomDoc inspired syntax. I'll definitely be adding something like the "prefs" thing in the top right corner of this style guide, that was awesome.

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 http://www.ali