I’ve been doing quite a lot of site mapping recently, and looking for a way to escape the standard boxy top-down view. In searching for examples of different ways to present the information, that are pleasing to look at but still immediately convey meaning, I found a number of interesting examples.
Below are the pick of the results, along with a few that don’t quite work, and some old standbys. I wanted to include images to illustrate this, but in most cases the license didn’t allow.
Following the recent push by Microsoft and Ascender to revive the EOT format for web fonts, debate has raged over the pros and cons of the two main alternatives: embedding and linking. Richard Rutter came up with the idea to license fonts on a monthly payment basis, with the font being served from the supplier’s server (or a trusted alternative).
I think there are a number of potential problems of practicality with that approach, many of which have been raised in the comments. As a contribution to the debate, I would like to offer the following suggestion:
Microsoft are trying to get people interested in the old EOT embedded font format by submitting it to the W3C as an open standard. Font foundry Ascender Corporation are behind them. I think this wouldn’t be an issue now if Microsoft had submitted this as an open standard five years ago, but that it may be too late now that their rivals are going down the route of font linking.
Anyone not reading this in an RSS feed will notice that I’ve installed a new theme. I was never really happy with the previous one, as it was based on a design that had been rejected from another project and was called into action before it was ready.
I’ve given this one a version number of 0.5, as I still have a lot I want to do with it, notably: embedding more microformats in the code; adding more progressive enhancement to the CSS; making more use of WordPress’ tagging system; and testing more thoroughly in IE.
However, I’m pretty pleased with the more typographic direction in this design, and am excited to be using a theme I genuinely care about.
If any readers have any constructive criticism to give, please go ahead and do so in the comments. However, do please be gentle with me!
Apple have released Safari 3.1 for Windows and OS X (and Linux using Wine) today, and the feature that really stood out for me was the introduction of web fonts. Website makers have been bound to the same core fonts for years now, so suddenly having a huge palette to choose from is going to make an enormous difference!
Using them is pretty easy. First you have to declare the fonts using the @font-face rule — and, importantly, you have to declare each variant (weight, style, etc) individually by linking to the font file involved. You can’t just link to the directory and let the browser work out the variants. To see what I mean, take a look at this example (using Safari 3.1, of course!) and view the source to see the CSS involved.