Ikiru Design

fdecomite

If there’s one problem in this ever-growing blogosphere, it’s that sites are so easy to create that no one worries too much when they die. So they continue to sit out here with the living, quickly becoming useless piles of bones that get in the way of the rest of us.

This is a problem in itself, but it’s one with which we can cope. We can cope so long as these bones aren’t intentionally made to look more alive than they are. So long as bones show themselves to clearly be bones, we living members are pretty able to avoid those we don’t really want to look at.

But a problem arises when you hide that your website is a skeleton. When you decide that you’ll get rid of post times or — and this is far, far worse — dates. Then when I come upon your site a quick glance around doesn’t tell me if I’m dealing with a skeleton or a living, breathing, changing blog

And if there’s one thing I less like than a dead blog, it’s a blog that doesn’t quickly fess to its deadness. Some otherwise great blogs and themes have this problem. I really like a lot about Brian Gardener’s Revolution theme, but I hate that no version puts publication times or dates on all the articles shown on the front page. Perhaps this was intentional or a simple oversight, but I don’t like it.

This is the internet age when lifespan of content is measured is hours, or — if we’re to be very generous — days. In such an atmosphere not telling me when your content was published is like admitting that you’re not a part of these exciting and rapidly changing times.

In some situations you could get away without times. Yahoo!, for example, doesn’t offer them on it’s homepage. And the Washington Post and LA Times are both lax about the times their stories were written. But they’ve got a great deal of built-in trust as well-known sources of information, and arguably important ones. A visitor can easily guess that, at most, the content is a day old.

But visitors to MyRandomSite don’t know who you are or what you do. They don’t know that they can trust that you’re not a pile of bones. So you need to tell them. Not much is needed; seeing “March 5, 2008” on a post is enough in most situations. That way I can tell that if nothing else, your site’s not a pile of bones. Maybe you’ve not updated in a few days or hours, but I know when you were last seen breathing. In a place where content’s cheap and credibility costs a great deal, that little bit matters a lot.

So please, bloggers, webmasters, web designer, and spectators, put a time stamp on your content. On your front page. Tell me that you’re not expired and I’m more likely to stick around and give what you’re doing some consideration. Thank you.

Armed with a firm desire to create a WordPress theme different from the others that I’ve made and little plan as to what that should look like, I made new theme that was first called “Small Verdana,” then “Old School,” and now the compromise “Retro Verdana.” It is, I suspect, ugly. But it’s also loaded with novelties I once loved and relished.

From the first webpages I ever made — with FrontPage, I must confess — Verdana was one of those fonts that I knew to use and even liked. I’ve also admired the false depth which is easily created by changing border colors. And I’ve always had a undeservedly strong affinity for the color #336699. And “Retro Verdana” has all of those things. And ugly as it may be, I like the result of combining those things. A lot.

To see this little beast for yourself, click here for a demo. Or, since you may well be too lazy, look right below this line.

Essentially, the issue is this: I have strong suspicion that “Retro Verdana” is ugly. Really ugly. Especially to modern tastes, but also to the timeless ideals to which I’d rather aspire. But I also can’t seem to avoid smiling every single time I see it. I can’t help saying: maybe you’re not the prettiest gal, but I’d still love to dance with you.

I can’t avoid the desire to post this theme and share it publicly even though I could be forever condemned as a victim of hideously bad taste. And I can’t avoid relishing in both the unsightly and the nice and novel features which, to even my surprise, I think it has.

So I guess the whole point is that I have two words to say to those who think it’s ugly: I understand. And I have two words for those who admit fondness for it: I understand.

You can download Retro Verdana here, and find its page here.

As I suggested earlier, I’ve been casting around for a plan that would assure that I didn’t again neglect Ikiru Design in the way I recently have been. This is both an issue for my free themes — which I first planned to have at 1.0 on January 1, then January 15, then ???, now ????? — and for general read-worthy content on this site.

On the first problem, I don’t yet have a good solution.

On the second, I have this: one post a week. This is meagre compared to the five a week I average at Frozen Toothpaste, and the five a day I average at Link Banana, but those are different sites with different topics and objectives. Once a week is a realistic goal which I feel confident I can achieve. This is roughly what I was doing before I took an almost accidental hiatus, and if I really commit to it I’m sure it’s something I can expect to manage.

This could also work to force me to do more work on my free themes, as in an inspiration-less week I could still have some easy-to-accomplish CSSing to fill the gap. That’s the new plan, and now that it’s public I hope I’m more likely to stick to it. And that’s not a lot, but it’s something.

I just changed the theme here back to the first theme I ever made: BWO. This is for a couple reasons, probably the most important is that I’ve been using Carter’s Line (which I was using here) at my link blog, Link Banana. It’s also because I’ve been negligent regarding this site and its themes. And I really would like to work on it more regularly.

As the title of these few paragraphs suggests, I’m not ready to say that I’m back to doing this regularly. But I’m thinking about how best to make sure I don’t neglect this so seriously in the future, while assuring that it doesn’t monopolize more time than I can give it.

I’ll be sure to let you know when I figure out a plan.

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.