The main advantage to using a css framework is speed. Once you figure out what the framework can do, it speeds up development quite a bit by helping to standardize the web development workflow. Blueprint can be the bridge between design and code., They’re especially great for those working on tight deadlines and those working in teams (teams wherein multiple people work on the same CSS — they benefit from having a consistent set of coding patterns), and also for those working on several sites of a similar nature (for example, a team working at a news company which runs 20+ newspaper sites). WHAT DOES BLUEPRINT HAVE TO OFFER? A CSS reset that eliminates the discrepancies across browsers. A solid grid that can support the most complex of layouts. Typography based on expert principles that predate the web. Form styles for great looking user interfaces. Print styles for making any webpage ready for paper. Plugins for buttons, tabs and sprites. Tools, editors, and templates for every step in your workflow. We used to offer wordpress development services in a minimum cost of $57 such a s conversion from html to wordpress and Design of wordpress themes from scratch, using these frameworks speedup the entire process and help us a lot to deliver the project on time with good quality . To start using Blueprint CSS framework this link will be helpful
If by 'speeding up development' you mean pissing all over accessibility, defeating the ENTIRE point of using HTML and CSS in the first place, destroying anything resembling separation of presentation from content, and making MORE WORK with MORE CODE... then sure. Particularly rubbish like blueprint -- vague/meaningless PRESENTATIONAL styles like "span-4", genuinely presentational styles like "highlight" or "border" -- at that point you might as well go back to writing HTML 3.2 for all the improvement it offers. It's just another of the things I cannot fathom how anyone is DUMB ENOUGH to try and use to build a website.
Gentleman, Please explore it .. dont be agressive gradually you can see that the framework is good. World is adopting it.. But it is up to you to use it or not ,But dont spread these agressive sentences.Amazed to see that you have more than 216 likes... but still not supporting new topics to learn and experiment.Every good thing starts with a painful attempt ,but the result will be fruitful.Lets take Microsoft MVC,PHP MVC ,Ajax even when people migrated from Dos to Windows no one was ready to use mouse.. Today No one is ready to go away from touch.. Now you tell me if i take you to that DOS generation ..then will you feel comfortable ? Why dont you at least support new things..If you can analyse it please compare traditional css with these frameworks and point out what we are missing here ... Good luck.
Actually, given that I released a DOS game for the 5150/Jr and Tandy 1K in 2011, and a Commodore 64 game this past November, PROBABLY not the person to say that to I've given most frameworks a serious look, INCLUDING blueprint. It's a sleazy half-assed shortcut which is why pretty much every site built with it has piss poor semantics, even worse accessibility, and on the whole reeks of people failing to grasp the point of HTML, the advantages of CSS, and a whole host of other shortcomings ranging from "WCAG, what's that?!?" right through to having one's head wedged up 1997's backside. I file it alongside all the other half-assed dumbass idiocy that's taken over web development like drawing goofy pictures in photoshop first, grids, px metric fonts, fixed widths, HTML 5, etc, etc... The only way you could get worse is the garbage like YUI, Bootstrap or HTML 5 Boilerplate... Which is the slippery slope leading to the road to failure... But of course, people LOVE their sleazy 'shortcuts' -- even when the result is garbage and usually ends up more work in the long run.