This is still my intention, but I am going to go a little further—having found that I can support all browsers through various techniques, I am going to restructure the blog in HTML5 (and checking it all in this HTML5 Outliner!).
HTML5 is logical and neat—especially for a blog format website. Replacing endless
divs with the new block-level elements—such as
articleall make reading the site structure so much easier.
Plus, of course, these elements allow for assistive software to recognise the page structure in a meaningful way, thereby increasing Accessibility—a subject that my recent article in Ability magazine expands on.
By the same token, I shall also be making extensive use of CSS3 and, as I intimated in my post about the iPad, deploying some effects—such as CSS animations—that will only work in the latest versions of Safari (and other Webkit-based browsers, e.g. Chrome).
All of this is as much to ensure that I continue to develop my coding skills, and learn the new syntax, as anything else. Naturally, however, The Kitchen will still be useable by every browser—but I do not intend to deliver the same experience to every browser.
For those who are interested, the rough browser breakdown for those visiting The Kitchen is as follows:
- Firefox: 40.97% (Rendering Engine: Gecko (Open Source))
- Internet Explorer: 34.22% (Rendering Engine: Trident (proprietary))
- Safari: 12.63% (Rendering Engine: WebKit (Open Source))
- Chrome: 7.11% (Rendering Engine: WebKit (Open Source))
- Opera: 2.90% (Rendering Engine: Presto (proprietary))
However, whilst all of this technical stuff might be interesting to your humble Devil—and sundry other geeks out there—it is, ultimately, you people who read this blog. As such, if you have any suggestions for the design—e.g. perhaps I should be using light text on a dark background—please feel free to sound off in the comments...