4 ms·
Blueprint to me seems like a conceptual step backwards. While it does still separate markup from style physically, conceptually it's just moving the layout desc
by compay 18y ago
Blueprint to me seems like a conceptual step backwards. While it does still separate markup from style physically, conceptually it's just moving the layout descriptions from the HTML attributes into the classes; there's 0 semantic value to the classes. It looks like the design still ends up being tightly coupled with the markup.
The results are beautiful, and I can see how designers might find it easier to work with conceptually. But from the perspective of a programmer I find it pretty unappealing.
- arockwell 18y agoI agree with you that its a step backwards, but I find that I have to add divs and classes all the type to my html that are there purely for layout reasons. Browser support just isn't there yet for truly semantic markup.
- cstejerean 18y agoblueprint is not a framework for something you should deploy a site on, it's a framework for prototyping and hacking on your layouts. the idea is to change it to something more semantic once you've figured things out (same way as an earlier article today mentioned using HSL instead of RGB for color prototyping and switching to RGB once you've figured it out).