Part of being a web professional is having to explain to clients that what they see on their screen isn’t what all of their visitors will see on theirs; differences in OS, fonts, browsers, and monitors all mean that there will be slight variations in the way your pages display. When it comes to HTML emails, it’s harder still; the differing levels of CSS support across the many, many email clients – both online and off- make it hard to establish who can see what.
It took me a while to see the benefits of microformats, but now I’m definitely there. In October 2006, the UK WSG meeting was all about microformats, and I decided it was too faddy, too niche for me, and that I wouldn’t bother. I regret that now.
The first thing that changed my mind for me was seeing Dan Cederholm’s presentation, Interface Design Juggling. He clearly explained their benefits, and made me think about ways my own sites could be enhanced by them.
The second thing was the suite of tools supplied by Technorati; the hCard and hCalendar convertors are easy ways to display how useful a little bit of standardised mark-up can be.
The third thing – and the real deal-clincher – was the Operator add-on for Firefox. This displays a small icon in the browser which alerts you to the presence of microformats on the page, then allows you to use the data for an amazing array of purposes; adding events to your calendar or contact details to your address book, searching for addresses in online maps, searching the leading social websites for related content… it really shows the potential of the semantic web.
For anyone still not convinced of the benefits of microformats, I urge you to install Operator and right-click on the following paragraph; once you see what you can do with it, you’re unlikely to remain unconvinced.
This post was written by Peter Gasston, who lives in Camberwell, South-East London in the United Kingdom. You can email him at peter@broken-links.com if you want to say hello.
Interesting times to be a web developer, as HTML 5 and CSS 3 are both on the (somewhat distant) horizon. I’ve just written about the Advanced Layout module on CSS3.info, IBM developer works have a nice introduction to the new elements of HTML 5, and Wikipedia has a chart of current browser implementation.
In a few(?) years time, a basic two-column plus header and footer page layout could be as simple and logical as:
body {
layout: "aa"
"bc"
"dd"; }
header { position: a; }
nav { position: b; }
section { position: c; }
footer { position: d; }
What a difference that would make to legibility.
A post called Trash All IE Hacks! on the (rather lovely) Web Designer Wall blog has attracted a huge amount of comments recently with its call to stop pandering to those who have the audacity to still be using the previous version of Internet Explorer (approx. 80% of visitors on one site I manage), and to display the broken layout as punishment for anyone not au fait with modern browsers.
Just in case you missed it, I was being sarcastic there; to take that attitude would be like a TV station transmitting black & white signals to anyone who hasn’t yet bought a High Definition set.
From the many supportive comments, a few said things like 85% of my time is wasted coding for IE6!
or I spent two nights getting the layout to work in IE6!
; to that, I can only reply: either you are doing something wrong, or you are a bad coder – or both.
It’s not hard to get sites to display properly in IE6; sure, you’ll have to put in a little extra effort, but it shouldn’t be anything like 85% of your time, or 50%, or even 10%. All you need to do is follow these five simple steps:
Jeffrey Zeldman: King of Web Standards serves as an interesting profile of the standardista, as well as being a history of standards and a primer on their importance.
Recently I was chatting with Rapha Martins, and he mentioned a feature he’d like to see in CSS: a ‘default’ value for properties; that is, if you change the value of a property, a keyword that would change it back to the browser default rather than you having to specify that value again.
That has been proposed for CSS 3, with the ‘initial‘ value, and it’s been introduced into the latest preview of Firefox 3 (Gran Paradiso), with the browser-specific -moz- prefix. I’ve put together a quick couple of basic examples of how it will work (you will, obviously, need the latest preview to see them).