Well, it’s not ready for primetime yet, but I got tired of not blogging, so here’s my heavily-customised WordPress-powered redesign. "A redesign?!?!", I hear you exclaim. "It looks exactly the bloody same!"
Well, yes, but my design skills are not exactly renowned, and when I checked my server logs, I discovered someone’s blog entry saying "I absolutely adore the site design of brucelawson.co.uk. So clean and simple, and yet it looks gorgeous. Fantastic stuff."
With praise like that, I decided to leave it pretty much as-is, though I’ve still work to do styling the new bits and bobs (comments, extra nav, post metadata etc).
There’s loads of stuff still to do, the biggest of which is the removal of all <br /> tags that snuck into the posts when I was copying from the notepad html source of my old site into the WordPress Post entry text box.
If anyone can donate me a PHP script that can replace <br /> with "" (only in posts), I will love you forever.
I’m enormously gratetul to Matt Mullenweg for WordPress as I now have categories, archives, permalinks, comments and all the trappings of your proper blogbloke. There were a couple of minor niggles that I’ll note in case they can be noted for WordPress 2.0:
- I’d love a check box next to the Post entry field that tells WordPress to ignore line breaks. It would’ve helped me when copying all the post from my hand-rolled blogs – and I’m sure other bloggers cut and paste from emails/ other web sites etc.
- I think the check box for "Edit timestamp" is overly belt-and -braces. As I was moving old blog entries, I repeatedly changed the drop-downs to select the date that I originally wrote the post, but forgot to check the box as well, causing no end of annoyance.
- In the theme that I studied in order to customise to make this aesthetic glory, there was a lot of presentational html – the <small> tag was common, as well as presentational class names like "alignleft". It might be cutting-edgily exemplary if they were removed for the next release.
But these are minor niggles. After only a few weeks (most of that spent copying and pasting old content), I now have a lovely database-driven website.
I pondered for a long time about whether to have comments on anything other than the technical category of Accessibility/ Web Standards, and have decided to have everything open to comments. So let the comment spam commence!