Styleguide [WIP]

This shot is basically a style guide I'm working on for a sideproject. Why a styleguide? Well partly because, I'd like to be able to design (and build) one. I also appreciate the intricacies that one has to go through when consolidating a product's elements into one single unified set.

As with everything, there are a number of questions that can be asked when thinking about, designing and building these styleguides (which ideally should be web-based and living rather than sitting on your desktop as a lonely PDF). Questions like "What kind of information do I really need from this particular section?", "What naming conventions are going to be adopted?" and "What cases apply to which component? When should I use [insert component here]?" are some of the things I've been asking myself (along with the people I'm collaborating with).