I’d been feeling a bit nonplussed for some time by the fact that I was using the WordPress default theme for the blog. But not nonplussed enough to actually do anything about it: I have other ways in which I’d generally prefer to use my limited free time, I don’t have strong design skills or a stack of photos lying around to select a header picture from, and whenever I browsed theme directories, I always found something to dislike in any theme that I saw. So I stuck with the default, with a few slight tweaks.
Over the last few months, though, I’ve run across more and more blogs and other web pages which took a very plain approach to layout. This is something I understand: I’ve read thousands of books that take that approach, why not use it on the web? So, last night, when I ran across one such blog that was using WordPress, I scrolled down to the bottom to see what theme it was using, and took a look.
The theme was basic2col. It’s a very plain theme; as the author says, “Basic2Col is just what it says – a basic two column theme for WordPress. The theme was created to have a basis for a new theme, but you can of course use it as is.” And I rather liked it as is, so I decided to download it today and give it a try.
After giving it more of a look, there were a few things I wasn’t thrilled about. Most notably, it sets the font size in the body to 70%. This is something that I see all the time, and I never understand: as a web user with aging eyes, I like to set the default font size in my browser to something that’s comfortable to me. So why do so many web pages feel compelled to disregard my preference? And, of course, they almost always override it to make the font smaller instead of bigger. Kids these days.
Fortunately, as mentioned above, the theme is designed to be customizable: in fact, the download page also contains a “customb2c” wrapper that lets you segregate your changes in separate files, for ease of upgrading. So one
body {
font-size: 100%;
}
later I was off and running. As a bonus, that also made the body wider, which was another thing that had bothered be about the original design.
I did a bit more poking around: I increased the margins here and there, I did some header bolding to give a bit more of a visual separation between posts, and I changed the sidebar a bit. But I mostly left it as-is, and I was pleased with how easy it was to do the tweaking I wanted.
Yours in simplicity,
Post Revisions:
This post has not been revised since publication.
There seems to be a widespread belief that users never scroll down, and if you don’t pack all your text on one page, it won’t get red. This may be true for advertising copy, but it’s nonsense for blogs — so if you don’t have little teeny eyes for reading little teeny print, please stick to default fonts! I have to set my default Firefox zoom to 150% to compensate.
9/28/2008 @ 11:12 pm
Ouch. “Read”, not “red”. You do need some sort of preview feature here.
9/28/2008 @ 11:13 pm
Keen points. I checked the default size of my blog and it was 70% as well with font-size x-small…I swiftly changed it to 110% and what a world of difference. Someone may actually read it now… :P
9/29/2008 @ 7:30 am
@John: Preview does sound like a good idea. Not sure when I’ll get around to it, alas… I hadn’t thought about the one-page idea, but that does make sense as a (bad) justification. But then why are there so many narrow blogs?
@Omari: Oh, that’s much better! I like your blog, but it made my eyes hurt. (Literally.) I’d been thinking of e-mailing you to ask if you might be convinced to switch it to black-on-white instead of white-on-black, but actually white-on-black with a larger font looks fine to me.
9/29/2008 @ 8:15 am