Breakthough!

Did quite a bit on the site today and had a bit of a breakthrough – I’d been exploring ways to get the latest blog post out of my WordPress blog and onto the homepage (which is a static page, not hosted within the blog) and finally I worked it out, thanks to various posts online, so now I have an auto-updating blog post on the homepage! Whee! Haven’t yet been able to get the Twitter feed working though, so I’ve hidden it for now. And I’ve got the navigation working correctly (highlighting the correct sub-navigation items) across all pages and I’ve added in a home link to the menu for pages which aren’t the homepage.

I also started testing properly in IE6 and I think I’m going to need the JavaScript fix Bruce Lawson talks about in Introducing HTML 5 to get the CSS to apply itself to the new HTML 5 elements that Our Friend doesn’t recognise. I was pretty amazed to see, though, that it’s picked up the fancy font, thanks to Font Squirrel’s easy-peasy generator… although, oddly enough, it has a problem with the blockier font. It’s nothing to do with the position of the definition – it doesn’t make a difference whether I move the blocky font definition to the top of the file, or whether I even remove the fancy font, it doesn’t show up in IE6, so I’m thinking it could be something within the font file itself. Not too disturbed though. After all… IE6 (although obviously I’ll have to see what it does in other versions of IE and that’s likely to do the same thing, I guess). Tossing up whether to put in an IE6 disclaimer. It might be a good idea. Just so that IE users know that what they’re seeing isn’t the actual design. While in general, I feel I should support any browser that is commonly in use, in practice, it’s getting ridiculous to still be fully supporting such ancient technology, when there’s a better, more semantic way to achieve things, so I’m thinking the hybrid approach – ensure all content is accessible, include a note letting IE6 users know that it’d be a better experience if they upgrade – is the best way to go.

Oh, and I made a cake. Chocolate, with chocolate ganache topping. And came to the conclusion that the oven thermometer my mama brought over with her has serious fail. I’m sure the oven’s running hot – it’s been burning everything at supposedly the correct temperatures. So I tested it out with the cake today – I cooked it at the official temperature on the oven dial, as always (because I know it works at that temperature, although it overcooks if you don’t keep a close eye on it) – 180 C, which the oven thermometer then said was only 160 C. Grrr. Might have to invest in another oven thermometer to see if it can do better.

Leave a Reply

Your email address will not be published.