In case you’ve been lost in all of the SXSWi hullabaloo, or just neck deep in work like myself, it seems the W3C HTML Working Group has decided using role=presentation on a table element is now conforming. So it seems after 5 years of fighting this out in the trenches, per one rebuttal to the proposal:
Over the past decade or more, Web designers have been moving away from tables for layout. For a while, limitations in the market leading Web browser made this somewhat impractical for sites with complicated flexible layouts that had to be compatible with a broad range of user agents, but this is no longer the case, and new sites can avoid using tables without difficulty. Old sites won’t change, but old sites are not affected by changes to conformance criteria, since they already exist. Conformance criteria only affect actively developed sites, and those can move away from tables (and many avoid using tables at all).
The counter argument from the working group:
This assertion does not mention a specific example. By contrast the authors of the proposal to make
conforming cite gmail, facebook, yahoo mail, numerous IBM applications, and toolkits such as DOJO and YUI. As each of these are actively maintained, we find that there was insufficient evidence provided to back up this assertion.
So Facebook prevails (again)? God help us all.
January 28th 2008
bad ass! Construct - a BluePrint custom grid maker that allows the addition of semantic classes and parses the html AND CSS
November 18th 2007 September 15th 2007
updated: New versions available. See bottom of post for details.
Mzingi development will no longer done on Bloggingmeta, as it’s now included in Habari’s core theme directory. Any bugs, comments, or suggestions should be pointed to Trac
I have had the idea for a foundation type theme for Habari since I first started working with the platform earlier in the year. After spending time converting k2 to the design for this site, as well as for my <a href://cookingwith.miklb.com”>cooking site, I knew that if I wanted to continue working on Habari theme design, I would need something else to work off of. No offense at all intended for the developers and users of k2, I have extreme respect for what it has achieved, I simply feel that it’s conversion to Habari was a difficult task, considering the advanced features in k2, vs being adapted to Habari at such an early stage. Andrew (aka freakrz), has done great work in advancing k2 to catch up to where the rest of Habari development is, however, I still felt I wanted my own framework to work off of.
That said, I took the initial work I had done here on Blogging Meta, and started working on a purely CSS based theme, that could be used out of the box, as well as be flexible enough to be used as a framework. I still have a long way to go in the design world, but trying to use all of the reading I’ve done, I think the markup is fairly semantic, HTML strict, and though the CSS validator chokes on the YUI font CSS, it should be valid CSS as well. I quite like the simple percentage based font sizing of the YUI CSS, as well as the built in font family cascading. Again, still plenty to learn in this direction, and perhaps at some point I’ll drop it, but it’s a good building block (perhaps after getting some time to mature, as well allow me to spend some time with it, I’ll convert to the Blue Print CSS framework). Aside from the YUI CSS, the only other borrowed code is from Andy Budd’s CSS Mastery chapter on forms. However, this will soon be removed, as I want the license for the theme to be completely compatible with the Apache License that Habari ships with, and Andy’s code is licensed under a Creative Commons share-a-like one. (A completely different subject, which I intend to blog about soon enough.) However, for the short term, the form is quite nice, and will suffice until I can write my own CSS for it. There was also a subconscious nod to the excellent Simpla WordPress theme by Phy Ly, though no conscious code borrowed from the design.
Also, many thanks to everyone on the #habari IRC channel for tips, tricks, and code help, particularly tinyau for helping with the comment form and ringmaster for help with the tag template code.
A few notes about the theme. The theme assumes the use of the tag “aside” for the asides in the sidebar, if you want to change that tag, you would need to edit theme.php and sidebar.php to change the corresponding tag. Likewise, if you want fewer or more asides or recent comments listed in the sidebar, you will need to edit those values in theme.php. I tried to comment the file to outline what the various additions are. There’s also the addition of the ability to an excerpt, as can be seen on the tag page.
So, without further ado, the first, alpha release of the theme is now available. I’m sure minor updates will come soon, but my impatience overcomes my need for perfection.
.2. change log.
Users of trunk >r1574
September 11th 2007
A few months ago, I came across Jon Hicks’ Mac inspired Google Reader, but recently noticed the version I was using was outdated, and Google Reader wasn’t looking so hot. Off I went in search of an update, and subsequent posts on Jon’s site, found User Styles. Though the site could use some better search functionality, I really like it in the sense that you can easily add styles via the Stylish extension for Firefox. I’ve employed Stylish for BaseCamp, and have thought more about how it could be used, User Styles gives plenty to think about now.