WordPress sandbox theme

If you are one of the handful of people not visiting this site for the first time (i.e. less than 10% of visitors), you’ll notice that for the first time since I installed wordpress, I’m not running the default theme anymore. Basically one of my reasons for installing wordpress was that despite enjoying the fiddling with html and css I got a bit tired of working around IE and mozilla incompatibilities, the many limitations of CSS and all the weird issues you run into when trying to achieve perfectly simple things like three column layouts. If you are interested in this stuff, there are several nice sites where you can read a lot of stuff about these issues.

Now, instead of getting my hands dirty, I decided to install the sandbox theme for wordpress available at plaintxt.org. This is somewhat of an experiment for me, basically my requirement is that the thing shouldn’t break down if I roll out upgrades for wordpress in the future. I simply want to keep that process as simple as possible: upload new wordpress php files and run the upgrade php script.

Basically, developing a wordpress theme means that these things become non trivial since with every update the theme needs to be tested again.

The sandbox theme has a few nice characteristics:

  • It is skinnable using ordinary CSS (i.e. like the good people at W3C have intended all web sites to be skinnable).
  • It generates particularly nice HTML. This always annoyed me in default wordpress and sort of took away my motivation to do something about making it look nicer in the browser.
  • Including nice little microformat class names for html elements where that makes a lot of sense.
  • It’s quite popular which means lots of people use it (so it is well tested) and which also means that it is likely to be updated as wordpress evolves.

Rather than develop my own CSS file for wordpress, I’ve decided to just pick one of the defaults that come with sandbox. I like the spartan skin since it is minimalistic and also tries to improve readability of the actual text. Overall it is quite nice to work with. Adding alternative sandbox css skins is particularly easy and I might actually do that since the spartan look is not quite minimalistic enough for my taste and also has a handful of issues with too small margins and paddings. On the other hand, I said the same about the wordpress theme when I migrated my blog to wordpress over a year ago (i.e. never happened). We’ll see what happens.

migrated to wordpress

I’ve been playing around with wordpress for about an hour. Easy to use, feature rich and I managed to migrate my old pivot posts by importing the RSS.

Why migrate away from pivot? Well, I wanted to try something new. Referrer and comment spam has caused me to cripple pivot and frankly, I never really liked the plain text files, the messy templates and the lack of updates during the half year I used it.

WordPress seems to be popular amongst the ‘hard core’ bloggers and I like the look and feel. Also the default template is much nicer IMHO.

As for that, I am unlikely to change it much due to a lack of time and interest. That may sound a little unlike me but I am sort of bored with trying to make html+css+javascript do things it is clearly not very well suited for.

I simply no longer believe in this technology: it is primitive, awfully limited and hopelessly flawed by design. Most nice page layouts consist of elaborate workarounds for browser limitations, browser incompatibilities, ambiguous standards interpretations and plain parser bugs. The implementation of the more relevant CSS features are almost without exception problematic.

I have no wish to learn much more than I already know about yesterdays mistakes at Netscape and Microsoft. Every attempt at building something nice over the past few years has ended with me discovering it wouldn’t work in IE (position:fixed) or it wasn’t possible at all (vertical spacing, css columns with a row beneath) or it would sort of half work in version x and break down in version y of Firefox (never bothered to find out which version was behaving ‘incorrectly’).