I totally agree with the concept, but I think you need to work a little more on the presentation: It's not obvious that Base, Layout, Modules and State are sep

I totally agree with the concept, but I think you need to work a little more on the presentation: It's not obvious that Base, Layout, Modules and State are separate articles when you've already defined them under Four Types. I assumed the links in the ToC were anchor links (I was on an Android). You also define Module before Layout in Four Types. You need to do something about the flow between the chapters. First of all: A big link to the next chapter at the bottom. Some of the chapters also ended a little abruptly (e.g. Applicability). Even though the chapters are quite small, it's still important to have some kind of "conclusion". It could be just one or two sentences, but you need to show that "I'm finished with this topic for now". I'd love to see more examples about different of modules. What modules do you almost always need in a project? When do you split one module into two? How small can a module be? How big? This seems very similar to OOCSS: http://www.slideshare.net/stubbornella/object-oriented-css http://www.slideshare.net/stubbornella/object-oriented-css. I can't find the right presentation right now, but Stubbornella had a great slide where she showed how often the Media-module is used in Facebook (it's everywhere!) and how much code was reduced by introducing it. That would be a great example for you too :-) Did you really work on Yahoo! Mail? Well, don't wait until chapter 2 to say it! I have no idea who you even are in the introduction. I mean, your name is only in the footer. Move your name to be a part of the title and tell what proper projects you've been working on (so I know I can trust you)!