[BP #3883] To Blueprint or not to Blueprint?

[noozillander]

Hi all, I recently emailed "Smashing Magazine" to suggest they do a simple "breaking out of the box" magazine-style html/css framework using Blueprint. i.e. not a framework that could just as easily be assembled with 3 columns and CSS. Here's what they said: We have already published this article on working with css frameworks, among them blueprint: http://www.smashingmagazine.com/2007/09/21/css-frameworks-css-reset-design-from-scratch/ However, we cannot recommend you to work with Blueprint. It's cross-browser functionalities are very limited. Instead we suggest you have a look at YAML which in terms of flexibility and cross-browser-stability is fare more advanced and it is very well documented. Yaml is not as easy to learn as Blueprint, however, it's worth the effort! The time will pay off in the future. Please have a look at this article on Smashing Magazine, which will help you working with CSS grids and YAML: http://www.smashingmagazine.com/2008/06/26/flexible-layouts-challenge-for-the-future/ I'm no expert, either with css or frameworks, so this statement about Blueprint kinda threw me, as I had heard good things about it. I don't want to dump this on your doorstep as I'll have to make up my own mind, but I'd sure welcome your POV on their comments. Thanks! John -- You received this message because you are subscribed to the Google Groups "Blueprint CSS" group. To post to this group, send email to blueprint...@googlegroups.com. To unsubscribe from this group, send email to blueprintcss+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/blueprintcss?hl=en.