linkdump for 2007.03.12

linkdump for 2007.03.07

copy of new tweets

Although I thought I would be taking a break from this darn thing, I saw a blog entry I thought was worth commenting on. Alex King asks what would be the proper behavior for a Twitter WordPress plugin. Given the inanity of my Twitter posts, I think the proper behavior would be to be not seen and not heard, but I imagine more felicitous users can say meaningful things in one-hundred-forty characters.

King would like a plug-in that checks his Twitter JSON feed regularly, imports his “tweets” (love the jargon) into a separate database table, and displays his status in a sidebar widget. This seems like the way to go, except given the ephemerality of tweets, I’m not sure I want to archive these posts. I understand owning your data and all, but I think setting up Creative-Commons licenses on the site is a higher priority.

One of King’s readers, Derek Punsalan, wants greater functionality from a Twidget. Punsalan would like readers to be able to leave comments on tweets, so asks to import tweets as blog posts. Lordy, lordy, lordy, people complain about blogs that merge posts and del.icio.us feeds. I can’t imagine the reaction to adding the banality of tweets to blog feeds. While I obviously think that doing daily del.icio.us linkdumps is a good medium between adding bookmarks as separate entries and ignoring del.icio.us altogether, I think a sidebar widget is definitely the way to go for tweets.

linkdump for 2007.03.06

on the rocks

Taking some more time off from blogs and blogging to refocus…
on the rocks

linkdump for 2007.03.05

mutiny of identity

Jon Gruber has an insightful post on default blog templates, and how they can undermine the branding work that goes on on blogs. He and Joe Trotter complain that default templates often look too standard, making it difficult to convey a sense of uniqueness. Gruber raises some important points disentangling the design of software like WordPress and Movable Type for the design of the presentation (i.e. the template.)

I’d add two things to this conversation comparing WordPress and Movable Type. First, WordPress’ templates (or “themes”) are very difficult to edit. Before someone jumps on me and insults my skills, I mean that the templates require too much literacy and investment for your average blogger, someone who’s made a Web page and may be wrapping her head around CSS. WordPress is very modular, so users need to hack up multiple PHP files, plus a stylesheet to make a substantial change. I haven’t used Movable Type in over a year, but the platform had relatively straightforward template files, and platform-specific tags, which didn’t require the user to parse PHP.

Secondly, the themes available for WordPress almost always use brittle CSS. They’re designed by people who want pixel-control over presentation, they often have weird leading and spacing issues. These themes look great “out of the box,” but if a user tries to tweak the typography or images, she often winds up dealing with broken presentation that requires more mucking about with CSS.

It’s no wonder so many WordPress blogs look like Kubrick or Hemingway with the colors and banner images changed. The templates are just too hard to edit. I’ve looked for a loose “wireframe” theme for WordPress to no avail. When I started banging on this theme, I thought I would create a theme, I could publish as a resource for other bloggers who want to get to know WordPress’ theme structure and be more creative with the platform, but I still haven’t found the time. I’m surprised I’ve found the time to write this.

linkdump for 2007.03.02

« Previous Page