Updating Blog Templates

When I first migrated my personal blog from Movable Type to WordPress I was just interested in getting it up and running as quickly as possible. After going through several themes I decided I would use Pixel.

I liked the dark look of Pixel and it seemed like an easy to read template. For the most part that template has worked. There were two issues though that just seemed to rub me the wrong way.

I wasn’t sure I really liked the background graphic but that is something that can be changed rather easily. The problem of course is that the background image wasn’t just the graphic itself but also included the area for the text and heading as well.

Still I didn’t have a lot of time to mess with things so I quickly created a graphic and put the theme in place. Since I was already in Photoshop I decided I would make a few other graphic files as well so that I could swap them out when I got tired of one.

That of course led to a modification of the Cascading Style Sheet (CSS) whereby the site would pull a different background graphic for each day of the month. After all why should I spend time changing background graphics when I can let the system change them for me automatically?

This theme was working and I figured I would just add the content and let it go its merry way. The more I started looking at it though the more I was bothered by the static width of the theme.

I’ve gotten used to the fluid width that CSS can provide and I really wanted my blog to be more fluid. The problem is that Pixel was based specifically on a static width. With a little time on my hands now that baseball season is over I decided to rewrite the code and make it a fluid theme.

I changed out the various areas and removed the static widths from the CSS. I recreated all of the graphics to be more fluid in width and in the end I had basically rewritten Pixel but as a fluid width template.

I really liked the rounded corners of the original graphics of Pixel but did not want to deal with the hassle of rounding corners with JavaScript, image files, and other hacks. Given CSS3’s corner rounding abilities I made a conscious decision to forego CSS 2.1 compliance and instead utilize the CSS3 code.

I used to stress over my coding making sure every single line was compliant but recently that has become less important to me. Life is too short to worry about whether my design looks good on old browsers.

Most of the users who visit my blog are using the newest generation of browser so I am not missing out on too much. For those who insist on still using Internet Explorer all I can say is I’m sorry but I refuse to cater to inferior technology so things look good for you.

It might sound harsh but if you want to experience this site and others around the Internet with the best experience possible I recommend upgrading to FireFox, Safari, or Google Chrome. You have no idea what you are missing.

For those with a next generation standards compliant browser I hope you enjoy the new fluid theme. This time I think I am content. Of course I said that three revisions ago so there’s no telling how long before I change it again.

Leave a Reply

Your email address will not be published. Required fields are marked *