If you want to use float-margin, you can still use clearfix to clear your content. So the templates are all fine, and we need no tables for layout.

In the example given on this page, “3 columns using float-margin”, add the following code to the “content2″ block (replace square brackets of course):

[div style="float:left"]float this left[/div]
[div style="clear:both"][/div]
[div]template is now broken[/div]

When you add the above code, the “broken” words are placed below the level of the “content1″ block. It is no longer flowing directly under the content2 text.

This is a problem where the “clear” appears in a column which is not as tall as one of the others. The text suddenly jumps to the lowest position on the page.

Therefore, using floats for layouts is ONLY practical if you NEVER need to use “clear:both” in your content.

I detest the decision to deny us the full usefulness of tables. Row height has been rendered useless, and this was a staple of many wonderful layouts. There was *no* real disadvantage, in the *real world*, to using tables.

As for using FLOATS for layout, that is *plagued* with problems. Try using a “clear:both” in any part of your body content, or menu content, and your template is destroyed. That’s because “clear” clears *all floats on the page* not just the last one encountered.

Using floats for templates is nicely conformist, but highly impractical unless you are very careful with page content so it doesn’t break the layout. That makes it a pain for CMS applications for a start.

The W3C is living in lala land when it comes to the needs of both designers and web app coders. If they just hadn’t deprecated table row height it wouldn’t be so bad. The fact they’re now formalising the “border-box” option in CSS3 means many, many people have complained! IE did have a valid position, no matter what the purists say.

/rant

I wish I had found this resource two years ago.

Just quick suggestion tho. It might be useful to include the year when you present dates.