Ikiru Design

The epic showdown. Two titans of free internet content-management will meet in this arena. Only one can emerge victorious.

Two things should be made clear at the outset: (1) I was looking to make a link blog, not a typical tumblelog with multiple kinds of posts, all formatted differently; and (2) I eventually chose (self-hosted) WordPress. Yes, I just killed the drama. But this is about a comparison, and not (as I implied in the last paragraph) about winners or losers.

There were, three battles in this war. The first is the one that only matters to the proprietor: the back-end. This focuses primarily on how easy it is to create and edit entries for such a blog. Second, and what was the deciding factor for me, was archiving. That is: how easy it is to find what you want among the old stuff. The final issue is rather nebulous, but we’ll call it flexibility. That being whether each CMS can do the splits.

The Back

This is, without question, the place where WordPress loses a lot of points. And where Tumblr shines, especially if you’re looking for more than a link blog.

Tumblr’s backend is stylish, as the image at right demonstrates. I could go all the way to elegant and perhaps beautiful. Essentially you select the kind of post you’re going to be making, and then you’re taken to a specific page that’s tailored for making that kind of post. If you haven’t played around with Tumblr, it might be worth signing up just to see this.

WordPress, on the other hand, is a hulking CMS which can do lots of things. But it’s not terribly elegant at any of them. The way I create a post for my link blog demonstrates well. On the top the title, post text, and tags are entered. Then the link is added down at the bottom in the “custom fields” area. In which I’ve had to create a custom field called “link,” in which I put URL I want this entry to point to.

The use of custom fields — by definition separate from WordPress’s normal working — also makes it slightly hard to style entries properly, and harder still to make the feed act correctly (a problem I still haven’t fixed on my blog). I don’t need to go into detail, but suffice it say that it’s a headache.

Advantage Tumbler

The Archives

This is where WordPress, comparatively, shines. And the reason that I decided to throw my lot in with the ugly backend of WordPress, rather than the snazzy ease of Tumblr.

Tumblrs archive (see random example) look nearly as fresh and innovative as Tumblr’s backend. When I first saw one I said: “Wow. This is cool!”

And even though all those statements are true, Tumblr’s Archives are troublesome. For one, I’m not a fan of horizontal scrolling, which any reasonably old blog would have. And the only way to search such archives is with a browser’s built-in search fuction — which works, but is hardly elegant. And the ability to navigate with tags, of which I’m becoming an ever bigger fan, is completely out as well.

By contrast, WordPress is built for archives. The archives page I’ve thrown together for my nascent link blog gives you some ideas. There are tags there, as well as categories and monthly archives. Sure there’s a lot less flash than Tumblr’s page, but this has something else that Tumblr doesn’t. The ability to search. Built-in. And search plus all the ways you can view a WordPress archive means a lot to me.

Advantage WordPress

Flexibility

As I mentioned at the start, this a rather nebulous category. It encompasses most everything that I haven’t mentioned but feel the need to.

Both Tumblr and WordPress have a large array of themes. For the purposes of tumbling or linkblogging, Tumblr’s better in this. As for the novice, some seemingly-complex things have to be done to any WordPress theme to make it work at all.

Both tumblr and WordPress can exist at their own domains (though the tumblr default is X.tumblr.com, it can be easily changed). Having said that, all Tumblr backend work happens at tumblr.com.

Also, if one is reasonably skilled, it should noted that WordPress can do much more than Tumblr. But many, not even myself, are reasonably skilled.

So for the novice Tumblr is probably a wise choice (note that I’m not wise), you can’t do many of the things that WordPress allows you — seperate pages, for example — but the ease-of-use is hard to beat.

This is hard to call, so I’ll go ahead and do it the easy way:

Novice: Advantage Tumblr

Level 3 Nerd: Advantage WordPress

Conclusions

This contest is hard to call. Each CMS got 1.5 points out of three. As I suggested, I would decide this based on nerdiness. If you’re comfortable with CSS, HTML, PHP, and WordPress, I think that’s the obvious choice. If the acronyms in the last sentence confused and disoriented you, Tumblr’s probably a wiser bet.

Forced to choose an overall winner, I think I’d choose Tumblr.

The only reason I’m not currently using it is that dislike it’s archiving system. And that I like the possibility for future improvement when I finally get smart and motivated enough.

I hope I clinched the choice for you, affirmed what you were alreay thinking. Neither system’s terrible. Neither systems perfect. It’s just important to choose the best one for your needs and abilities.

I recently redesigned my non-design blog, Frozen Toothpaste, and did it with a variation of the BWO_one theme. At first I was very hesitant to go with a BWO_one variant because it meant that I’d lose the sidebar which the theme I had been using, Chris Pearson’s Copyblogger had had. It was some of the arguments that I’ll present here that convinced me that that would be OK.

Now, I should be clear that this is not an argument that no blog (or other website) should have a sidebar. I think they’re incredibly useful in a lot of cases. When I surf the blogosphere, I tend to favor the sidebar as a way to get around.

But the sidebar’s usefulness gives way to one of it’s biggest flaws: the clutter problem. Bloggers — who tend to be novice designers — tend to dump anything and everything into the sidebar. Most people probably have seen this problem before, but if you doubt me go spend a little time looking though blogspot.com or wordpress.com, you’ll notice what I’m talking about.

The problem starts benignly when a new blogger will say: “I want a little note to be easily visible,” and they’ll dump it into the sidebar. They’ll say “I want a RSS subscription button (or perhaps one for every feedreader known to man)” and that’ll go in the sidebar. They’ll create multiple blogrolls, and then a few images and maybe some links to their own content. And they’ll ad a last.fm widget, and a flickr widget, and a translations widget, and the “awards” they got from other bloggers. And it’ll all go into the sidebar. By the time they’re done no one wants to see, let alone click on the cluttered mess that resides where a simple sidebar used to.

I’ll readily admit that this story is a slight exaggeration. Many sidebars are manageable while they contain all the desired content. But that doesn’t change the fact that sidebars have latent tendency to become ugly and unmanaged clutter magnets.

Another strong argument for banishing the sidebar is that, especially but no exclusively when weighted down with moving widgets, they’re a hideous distraction from your writing. This may not be a concern for some bloggers, but I’d bet that the vast majority of people who blog do it as a way to practice, polish, and improve their writing. You want readers to look at and comment on what you’re writing, not be whisked off to yet another blog.

It not that a sidebar is an unavoidably bad, or that it shouldn’t be used. The issue is primarily that one must consider if they really need a sidebar. If you don’t it’s far better to use a design without a sidebar than to persist in having one that offers no function you desire.

There are risks in eliminating it certainly. But for every visitor that’ll be turned off by your lack of a sidebar, at least one more will be interested enough to try to see why you’ve eliminated it. It’s not that ever site should either have or not have have one, but every person designing for blogs should think about their merits and problems before making more of them.

The Economist is without question my favorite newsmagazine. Where Time and Newsweek have spent a great deal of that last decade covering more about trends and celebrities, The Economist stays nearly as constant and high-minded as its title would suggest. And though both of those traits can sometimes be bad things, in this case I quite like them. No other publication gives you regular updates about what’s happening in so many places around the world. And I feel confident in saying that no one on the entire planet (with the possible exception of its editors) knows everything in an issue of The Economist before they read it.

Having said all of that, the magazine’s website is a little drab. Though I like the simple functionality of the “current issue” page, it’s not exactly a groundbreaking layout. The frontpage is also admirable-but-boring, giving you a quick snapshot of some of the sites freshest and most interesting content while doing a great deal to prevent the overload that comes from many magazines and newspapers.

But I recently ventured into the publication’s rather modest blog section, and I feel confident in saying that I understand why the commenters are so few and far between. The section feels rather like an afterthought.

But the biggest problem The Economist’s blogs seem to have — and this isn’t a problem particular too them — is that they look so darn boring. Their economics blog, Free exchange, does a very admirable job highlighting the problem. Upon loading the page, my first though was: “I’m supposed to read this!?” And remember: I’m an ardent fanboy of this publication.

Now before I lay into The Economist too hard, I will readily admit that I experience this often with blogs, even my own (which any fool could tell you I value much more than those of others). Large blocks of smallish text, especially in a readable-but-slightly-dull face like Verdana or Arial, is a sure way to make me think a little before reading. And as anyone experienced in the use of Digg of StumbleUpon can tell you, that second’s hesitation may well send away over half of those who arrive on the page.

Now I dislike those that to tell you that you should front-load a post with photos and pull-quotes and other eye-catching tricky to convince fools to stick around. But after looking at the blogs of The Economist I know understand the advice in a way I didn’t before. I would never advocate pictures for every blog and entry, but they can certainly make things seem a little less drab.

To avoid giving the canned “use pictures” advice, I’ve thought of a few ideas that I think could help improve the blogs of The Economist and probably could improve yours as well.

• Subtitles for blogs. The first sin Free Exchange commits is that it doesn’t tell me what I’ll find there. If I’m a quick thinker, I may make the inference that the title probably refers to something like commerce, trade, stock markets, or economics. Were I a fool (and we shan’t ever forget that I am) I would probably say “Hmm…” and either leave the site or look down the blog.
• Subtitles for content. If there is a single flaw that almost every blog on the planet (mine included) has, it’s that you don’t have more to go on before diving in than than the few words that make up a post’s title. But even the most pithy title can strongly benefit from an intriguing subtitle, as both Slate and Salon illustrate (in randomly selected articles).
• Too much sidebar. This is harder one to judge, and a much harder one to agree on. Some think that sidebars should be stuffed or exploding, I certainly don’t. One of the strongest arguments against a sizable sidebar is made by Free Exchange: a interesting sidebar easily distracts attention from your boring-looking content. This (too wide) sidebar is distracting with its ads and pictures and colorful tag cloud. All of these things make me more likely to click around (and perhaps away) and less likely to realize how good and useful the blog’s contents are.
• Hard to get around. The Economist seems to be struggling mightily to hide their blog content from outsiders. Not only is it hard to click to the site’s other blogs when you’re in one, but it’s hard to find content within that blog. Other than the distracting tag cloud, there’s the thin-and-nearly-hidden link to their month-by-month archive and a list of recent posts. All of these are rather standards in the blogsphere, but they’re hardly good. The site’s Archives page, when you finally find it, look suspiciously like the default WordPress archive that I’ve worked to correct twice before.

Those four issues certainly aren’t an exhaustive list of the (disputable) flaws in The Economist’s blogs. The clearly-broken look of their American politics blog Democracy in America is perhaps a greater sin than any of the above bullets. But I’m glad to have noticed these sins, and hope they can be instructive in my (and perhaps your) future work.

A while ago I promised that all of my currently-available themes would be updated to version 1.0 by January 1, 2008. Today is January 1, 2008 and not a single one of them is at 1.0. I did start the process, and make noticeable improvements. Carter’s Line, BWO, and BWO_one are now all at 0.80.

But that still leaves BWO_space and BWO_doodle behind. And it leaves some problems I have with the current 0.80 releases intact. So I can’t declare success on this goal, and I don’t foresee being able to do so today.

I do have a number of excuses to claim for my failure. There’s of course the unexpected holiday chaos (which I should probably expect by now), my recent decision to start a new blog, and the fact that I simply found the updates — a rather tedious and dull activity because the errors across these themes are very similar — too boring to spend much time on.

None of these excuses count for much, and so perhaps the most important point is this: I will have the updates done ASAP, and certainly no later than January 15. The penalty for not making that deadline is death.