I disagree with first quoted sentence below and the general premise of the article. True, Blueprint does force you to add some proprietary classes to your XHTML elements to dictate layout on a grid. But, your elements don't have to be divs, and you can still use additional classes to articulate the full semantic meaning of the element.

All in all, it's a small price to pay to speed up Web development. I have found I can whip up a nicely laid out site that works on all browsers *much* faster with Blueprint than I could without it. And, because there is a set of naming conventions, it makes it much easier for a team of developers (or if using a CMS, the content creators) to specify and read each others' layouts.

Quoted: A CSS framework passively removes a great majority of semantic value from the markup of a document and, in my opinion, should be avoided. This lack of semantic value works against a big part of what Web Standards are all about; creating documents with rich semantic value.

Looks promising. I know some WordPress themes make use of this.

Quoted: Blueprint is a CSS framework, which aims to cut down on your CSS development time. It gives you a solid CSS foundation to build your project on top of, with an easy-to-use grid, sensible typography, and even a stylesheet for printing.

This is a handy feature of Google Docs I didn't know about...

Quoted: A new (to us) item in the Edit pulldown menu lets you apply standard CSS styles to your Google Doc. A Google Group exists to help you work out any kinks in the process, and a Googler offers a beautiful resume template (available for you to copy into your own Docs account) all styled with CSS.

Highly recommended. With html + css, there are many ways to do different things (tabs, font sizing, etc.). This book gives you the "best" and most "bulletproof" way based on the author's own experience as a web developer.

Quoted: Each chapter starts out with an example of what Dan refers to as an “unbulletproof” concept—an existing site that employs a traditional approach and its associated pitfalls. Dan then deconstructs that approach, noting its downsides and then making the site over using Cascading Style Sheets (CSS). By the end of each chapter, you’ll have replaced traditional, bloated, inaccessible page components with lean markup and CSS. The guide culminates with a chapter that pieces together all of the page components discussed in prior chapters into a single page template.

Helpful if you want your webpage to look right in IE6.

Quoted: This page links to various Explorer specific bug pages.

Noticing this bug at the moment:(

Quoted: In Explorer for Windows there are two display errors. One, the container is only containing the last line of floats , and the floats are also running off to the right, all the way to the right screen edge! Take it from me, folks, that is not kosher.
...
Screenshot in IE6

An explanation of why margins are collapsed in css...

Quoted: Why is this? Because it's what authors would tend to expect. If you declare top and bottom margins of 1em for paragraphs, odds are that you want one em of space between successive paragraphs. If you're feeling dubious about that assertion, consider this:

Pretty helpful if you need to style a table.