Just over a year ago I retired my old “The Humanaught” moniker and replaced it with the current domain. The change-over brought in a new site design — but not one I was ever overly happy with structurally. It had some things I liked, and a bunch of awkward things that I was constantly working around.
So the other day I decided enough was enough and started fresh. As this is my personal blog, I wanted a design that was fun, interesting and showcased various things I like. I also wanted a bit of a sandbox that I could play in with new CSS3 and HTML5 goodness. And so the 2012 edition of the site was born.
One of my objectives was to make the site lighter (in weight, not colour), but still be a bit of a visual smack in the face. As such I’m using CSS instead of images for display elements wherever possible — true, this is a good practice all around, but one that is easily ignored or forgotten when you’re eager to get things “just so”. Fortunately CSS3 support is pretty much across the board now (thanks for joining the group IE9, your dusty nametag is by the door), and that opens up a huge palette for a Web designer to play with.
This has resulted in a theme that uses only about 10KB of “layout” images, not counting the various background photos (which can be customized page-by-page — see the about page) or the slightly heavier home page due to those big social icons.
However, if you still happen to be using an old browser, things are going to look a bit sketchy for you. I spend a lot of time making client sites backwards compatible, and it’s frustrating. Next to bookkeeping, it’s about the most mundane and irritating part of my gig. The truly insulting bit is that there are few things simpler than upgrading to a modern browser, and yet people refuse to do so. And this is why for my site, my site, I’ve said “to hell with it” and have barely given those fools a code line of consideration (if you are part of the 2% that come here using IE6 or IE7, I just called you a fool, de-fooling yourself is easy). A modern Web experience and browser security obviously isn’t a priority to people who are using 10-year-old browser tech, and I’d be doing them a disservice by enabling them to continue using it.
Anyway, the design still has little ways to go, and there are lots of small (and largely long-forgotten) legacy things that will need to be dealt with (the downside to running this blog for a little more than 8 years now — seven of which have been in China — is that the way I laid things out in the past is a far cry from the more standard way I do things now, lesson learned).
One other change is that I’ve done away with Disqus for comments. As a rule, I try to avoid 3rd party integration for things that core software does well enough. I wanted to give Disqus a try though and so had installed it with the last update (a year ago). Overall, I like Disqus’ functionality, and I like that it pretty seamlessly can be enabled and disabled (you’ll notice all comments made during my Disqus trial are still there and still in the proper hierarchy). It also has some great SNS integration. However, I do a lot of work with WordPress, and I’m used to the WordPress way of managing comments. Because of that, the Disqus system never really felt comfortable to me.
I think that about covers it. Hopefully the new theme is as enjoyable to visit as it was to put together.