I’ve been doing a bit of thinking recently.
I’ve been thinking about HTML 5 and the new semantic sectioning elements it proposes to introduce: header, footer, section, article, nav and aside.
I’ve also been thinking about the way microformats use data format standards and reserved class and id values to organise content.
Then thinking about this 2005 research into reused class names, which shows that, probably mostly unconsciously, website makers were already using the proposed HTML 5 elements as class names to organise their data.
Read the full article
[We work] with email client developers and the design community to improve web standards support and accessibility in email.
The Email Standards Project
It’s fair to say that a large chunk of the web industry now understands the importance of standards; from browser makers to designer/developers, we’ve taken on board the years of evangelising by early adopters and in turn it informs everything we do (I sincerely hope I’m speaking for the majority here).
But there’s one area of web development where standards break down; where we place elements where they’re not supposed to go, where we (whisper it) use tables for layout. Not because we want to, but because we have to. That area is, of course, HTML emails.
Read the full article
The October 2007 issue of the UK web development magazine .net has an interesting feature this month where web professionals share their favourite tips for coding CSS. Here are the five tips, with links to read more about them.
Read the full article
So @media 2007 is over and, after a little breather, here’s a short breakdown of what I saw, in chronological order, along with links to presentations where possible.
There were lots of great, inspiring ideas, which should spin out into a few more posts in the near future.
Read the full article