It’s time for a CSS3 @font-face browser support table. One that documents specifically how browsers act when either the whole font family is specified (regular, italic, bold, bold-italic & small-caps) or only the regular version of the font is specified. The test-case that this based on uses the ideal, easiest (laziest) implementation and can be found on its own page here.
Just a quick note to commemorate a design refresh of this site. Have been looking for ways to create separate attention for main text and the sidebar. Can’t say I haven’t been inspired by Jon Hicks (and others) who has also just implemented a differing-colour-main-part-with-border on his site. Kept the main nav in the middle, to add ugliness give the design a quirky edge. If I have time to put the search-bar up top the nav may be able to move over to the left.
Accessibility. It’s not just blind people. It’s not just for the real world either. For websites it means providing a useful site to anyone. In the early days of the web, there wasn’t much information out there for web designers and it was off everyone’s radar.
Good news! Google Chrome is getting full page zoom, and it’s the default! That only leaves Safari to implement it, as IE, Firefox & Opera have had it for a while now. 
Second in a series of articles about tinkering with improving your WordPress installation, we return to custom 404 error pages; adding a list of possibly related posts when visitors have followed an outdated link. Other 404 error page improvements can be found in the first article of this series.
First in a series of articles about tinkering with improving your wordpress installation, today we tackle custom 404 error pages; the page everyone dreads getting when they’ve followed an outdated link.
Bug reporting is tricky. Bugs are problems in software where the software doesn’t work as it should. “It doesn’t work.” doesn’t get you anywhere with the developer of the software in question, so the key is to report exactly what happend and what should happen very clearly. Steven Frank (of Panic, Inc. software-makers) has made a list explaining what you should and shouldn’t do when reporting bugs. One of the things Frank specifically mentions as being good ways to convey bug reports are images and video.
You used to have to choose. Choose between an easy, but inflexible, px-based layout or a hard to control, but flexible, em-based layout.
Coming up in March is the next South by Southwest (SXSW) Interactive conference. It’s one of the biggest gatherings of new media people (meaning web folk) and it’s held in Texas. The conference time-table is filled with talks. Who gets to talk at SXSW? That gets decided by online vote. While that seems like a neat idea at first, it has attracted criticism for not delivering a quality panel line-up.
Over the past year there’s been a lot of attention (in certain circles) for “microformats”. Essentially, microformats are standardisations of class-values to use in html. The implied benefit is that any 3rd party (be it a browser or another site) could easily gain access to that information and be able to do something useful with it.