I don’t think I’ll be going out on a limb if I predict that the hot topic of 2009 will be HTML5, the proposed update to the markup language which acts as the foundation to everything we (web monkeys) do.
This week saw the publication of a few articles on the subject written by respected members of our industry. While a lot has been written already about the potential of the new language, these are notable for their more practical approach.
2008 was pretty exciting on the web, wasn’t it? The continuing rise of social media, mobile internet, APIs, frameworks… it’s getting harder to keep up with it all.
I won’t be so bold as to make any specific predictions about the year ahead – more of the same is my best guess! – but here are a few articles I’ve read recently which have an eye on the future.
The last month has seen me completely immersed in User Experience theory and Information Architecture for my new role, and it’s been a very hectic time. While that hasn’t stopped me from keeping an eye on developments on the web, it’s given me less time to write about them.
Here’s a quick round-up of a few links that have grabbed my interest over the past weeks; I’d like to write more about them, but time forbids.
A new beta of the W3C Markup Validator has been released, and the best news is that it supports the HTML 5 doctype, <!DOCTYPE html>.
This doctype will trigger standards mode in all current browsers, so you can start using it straight away*, secure in the knowledge that you can still validate your code.
* Note: See the first comment, below.
I’ve just finished reading John Allsopp’s book ‘Microformats: empowering your markup for Web 2.0‘, and thought it deserved a review here – marked up, of course, with hReview. I was given a free copy at the recent Microformats vEvent, but hope that hasn’t coloured my review at all. Markup for the review was generated by the hReview creator (and slightly modified by myself).
Just implemented phase one of my mark-up plans, by implementing hAtom across the site; you can check it with Optimus, although be aware that it’s Optimus that’s producing the errors, not me! Of course there’s no massive benefit in my using hAtom at the moment, but a little further down the line I’m sure I’ll be grateful – plus, it’s good practice.