Preparing for Dinner
Thursday, February 23rd, 2006

I’ve been quite busy with some other webbie things lately. That is by no means an excuse for not blogging here. I don’t write here much because I really can’t be arsed…I often find writing quite difficult. This is one of those times.
That is why what’s coming next may shock you…I’ve created two new blogs!
While in London I purchased a lovely new camera and have been happily snapping away. Thanks to flickr keeping all the shots in order is relatively simple. I do however find it a little (and only a very very little) frustrating that one can’t ‘favorite’ ones own photos in flickr. I’m finding that with the new equipment I’m ending up with quite a few shots that I particularly like. This is why I now have a photo blog. It’s a place for me to catalog the shots that I love. I’ll try to post 5 photos a week…weather permitting. I find it a lot easier to take a photo and upload it than to think of something to write about for this blog.
Have a look, leave a comment, take more photos!
Along with all the photos there is also a lot of food! We love cooking! (Me particularly.) So Manda came up with a lovely idea - a dairy-free recipe blog. It’s Kai Time is a collection of of the recipes we use a lot. We’ve added star ratings so you-all can see how much we love each meal.
Have a look, leave a comment, cook more food!
During the past 9 months or so I’ve been lucky enough to build quite a few CSS based websites. I learned quite a few things during these builds - from cool layout techniques to PNG24 IE hacks (dont ask). One thing I noticed during each of these builds was that I kept going back to previous builds to reuse bits of code I’d written before. That got tired real quick - so I decided to create a very basic yet robust CSS ‘framework’ (for lack of a better word).
So without further ado…here we go:
My method uses 3 main style sheets per website. These should be included using the normal <link /> element.
<link rel="stylesheet" type="text/css" title="sitename" href="/css/style.css" media="screen" />
<link rel="stylesheet" type="text/css" title="sitename" href="/css/print.css" media="print" />
<!--[if IE]>
<link rel="stylesheet" type="text/css" title="sitename" href="/css/iehacks.css" />
< ![endif]-->
The iehacks.css file is included using IE Conditional Comments. This is to ensure that the sites are future proofed (with the eminent release of IE7 this is quite important from a hacks management point of view). There should never be any IE hacks in the style.css file. This file should contain only valid css designed for compliant browsers.
The print.css file will contain CSS used only for the printing of the website. Typically this file will hide the nav, BG images and any other non-printable stuff. Due to the very cool media=”print” attribute/value pair on the link element making PHP print versions of sites/pages is a thing of the past.
The style.css file contains includes to other very generic CSS files as well as site specific CSS. A typical style.css file contains the following sections:
I would typically add my site specific CSS directly into the style.css file thus keeping the seperate CSS files as generic as possible. For your conveniance I’ve provided a zip file with all the CSS files included. This is very basic CSS so don’t expect this to be all the code you’ll ever need.



