Technosailor.com Readers! Donate today to assist the Internews Haiti Earthquake Communications Effort in their efforts.

24 July 2006 251 Comments

But, it doesn’t act like a blog!

You may notice some changes happening here at Technosailor. On the surface, the changes look simply like a design change. Most of the time in the past, when I have come out with new design changes they are generally live in a period of a day or two. But this is more than a design change and it has taken me two weeks to get to this point. It is a completely new blog concept and is likely the most challenging thing I’ve ever set about to do.

About two weeks ago, I began an email conversation with several people who I hand chose as experts in the area of 1) blog design, 2) blog usability and 3) blog marketing. I asked them for feedback on the concepts I had in my my mind. This is the email I sent in its entirety:

I picked you four to send this email to because of all the people I know, you have the most conceptual grasp on blog architecture and effectiveness.

By now, you are all probably aware that Technosailor is about to undergo some massive changes in architecture. I wrote about one such aspect today in case you missed it.

So the theory is to have multiple views. Initially, the thought was to have the standard view, a conversation view (which I wrote about) and a reddit like view for readers to vote stuff up or down and the most popular stuff would float to the top. However, as radical as the reddit-like view sounds, I’m beginning to question the wisdom.

For one, I have a ton of content already (2.5 years worth) and no one is going to go start rating older stuff now. Theoretically, it would be a “from now on” thing but that makes results very biased. Plus I just don’t know how many people will “get it” in terms of the concept. If I had a Lifehacker type blog, perhaps. I don’t so I’m beginning to question the sanity of building such a system.

Other ideas for a third view is to have a “Popular” view that is based on number of comments but that is inevitably going to pull alot of really sort of irrelevant content up. Another idea was to do as Pearson has suggested somewhere (can’t remember which entry he commented on and where) which is more like a “Best of” view, but that would require going through 2.5 years of content and finding what I think is the best content. That could be a tedious process as well. Both of these other two options aren’t nearly as sexy as a reddit-like view either.

So I’m looking for advice or ideas on a third view that is 1) effective for advertising, 2) effective for exploration, and 3) creates a “wow” in the blogosphere. While the ideas I’m searching for might be intertwined with the actual design, I’m really grasping for more conceptual ideas in terms of architecture.

So, that said… any of you have any advice?

The conversation that ensued highlighted some key philisophical differences between the parties involved but ultimately resulted in some really good feedback.

Brian Clark from Copyblogger made these comments:

Any good blogger, publisher or producer is no doubt listening carefully to the crowd. But the true value of that listener is in what he or she does with the fruits of the observation, not in regurgitating it. If the blogger is not smarter than the crowd on a particular topic, or doesn’t have a fresh perspective, why bother?

So, any Digg or Reddit feature should be just that… a feature. And a tiered rating system would seem to deliver more valuable feedback than a simple “bump it up the page” system. It’s not whether someone likes it or hates it. It’s the shades of grey in between that provide insight.

The real value in information architecture is the placement of what Aaron, or Darren, or Jeremy, or Chris thinks is important. In other words, the most valuable content real estate on a blog should be less automated, not more, because it takes a real live editor to make those decisions based on what he observes and further deduces.

Brian goes on to suggest really highlighting “Best of” stuff as the predominant feature of the new blog experience. Jeremy, however, disagreed:

While I love these thoughts, I’m a bit curious how these get applied in an actual blog setting.

Not that I don’t love the thoughts. It’s no big secret that we’re about to launch v2 of our publishing platform at b5, and that we’re [b5media] already looking for great ideas for v3 (since, really, v2 is what v1 was supposed to have been but never lived up to).

Chris Pearson decided to weigh in on the side of “the more effective sidebar, the better”:

Personally, I have found huge value on my own site in the modules that lie in the right sidebar. I update the links over there on a semi regular basis, and they have done an excellent job of raising (and maintaining) my overall level of page views and site “stickiness.”

Despite their initial success, I believe that these modules could still be arranged (or rearranged) in such a way as to bolster page views and drive traffic to different parts of my site. Think of it along the same lines as CPM and Google ad placement – some areas are just more effective than others, plain and simple.

Structure

With the opinion of three crucial guys in my pocket, I set about to brainstorming on how I actually wanted to accomplish this new blog experience. I decided that I wanted to keep a conventional blog view where most recent posts are listed from the top down. Most blogs are like this and to take this view away could possibly disorient readers.

Secondly, I wanted to have a “Best of” view. I decided to nix the concept of Reddit voting in favor of this view. This wil be a subselection of what I view as my best content. through the years. As other entries are written that reflect that feeling on my part, I will continue to add articles for this view. It serves mostly as a high-level view of my writing and a good jumping off place for new readers or search engine readers who would like a snapshot of my content.

Finally, there is the most radical shift away from conventional blog architecture and the bit that took the most time and heartache to create. It is the Conversation mode where democracy is the name ofe game. As readers comment on content, no matter how old, it will rise to the top. The most recent contribution to conversation will be listed first. I think readers will like this mode as sometimes older content gets attention but no one knows that because it is off the front page. This view changes that.

I also decided to make the views cookie based so that readers can return to the site at a later time and have the same view as they left with. Props to Andy Skelton and #wordpress IRC user leftjustified for key bits of help along the way that played into the final product.

Design

The design was the second phase of this overhaul. My stats claim that only 2% of readers use 800×600 resolution. Most accessibility experts think that every site should be viewable at minimum at 800×600 and up until this design, I have followed those guidelines. However, designing for 800×600 is very limiting. I decided instead to support 1024×768 minimum for this overhaul. In fact, I also decided I wanted to move away from fixed-width layouts and to embrace fluid layouts (they adjust with the screen size). I also wanted minimalism to be the key.

I abhor design work but I began working out some concept pieces. Most of them I scrapped after a day or so before I settled on this design. It returns to the roots of “nautical” imagery that I’ve always used in the past up until the last design. I roughed up the concept that includes three columns, a prominent bit of real estate for ads in the upper right corenr, and a functional banner that allows users to switch between the blogs views.

I handed the design over to uber-designer Jonic Linley who dressed the design up, decided to pimp my feed in the banner and worked his CSS magic to make the site leap off the page.

What you see in front of you is the product of lots of hard work, thought and really key contributions from key people. I’m really proud of this concept and I hope that it will spark further discussion in the blogosphere about blog architecture. Overall, we’re in a rut. If my design causes people to think about blog architecture and think outside of the proverbial box, then my job is done.

As a sidenote, all the functionality of the views is in a plugin. I may release it later on for a fee, or possibly free under GPL. I don’t know. Depends on the demand. Let me know.

Please let me know if you run into bugs. It’s been tested on IE6, IE7, Firefox 1.5, Firefox 2.0, Mozilla 1.7, Opera 9, Safari 2.03 and Firefox/Mac.

Update: Bugs already. :) Couldn’t have guessed. Archives are currently broken. Fixing that. Comments template was missing. Fixed that. And my “views” makes alters the order of entries in my admin. Grrrrr. Okay, well that doesn’t affect anyone but me but it means I have to go work out more on that front.

Pick up your copy of the WordPress Bible, a wildly popular resource for beginners and experts alike.

Popularity: 2% [?]

251 Responses to “But, it doesn’t act like a blog!”

  1. Aaron 27 July 2006 at 3:07 pm #

    Hart: Um, yeah. You need to upgrade. ;) 2.0.4 will be out in days. Recommend you upgrade then as there are significant security issues that are resolved in it that affects all previous versions of WP.

  2. Aaron 27 July 2006 at 3:07 pm #

    Hart: Um, yeah. You need to upgrade. ;) 2.0.4 will be out in days. Recommend you upgrade then as there are significant security issues that are resolved in it that affects all previous versions of WP.

  3. Aaron 27 July 2006 at 3:07 pm #

    Hart: Um, yeah. You need to upgrade. ;) 2.0.4 will be out in days. Recommend you upgrade then as there are significant security issues that are resolved in it that affects all previous versions of WP.

  4. Aaron 27 July 2006 at 3:07 pm #

    Hart: Um, yeah. You need to upgrade. ;) 2.0.4 will be out in days. Recommend you upgrade then as there are significant security issues that are resolved in it that affects all previous versions of WP.

  5. Aaron 27 July 2006 at 3:07 pm #

    Hart: Um, yeah. You need to upgrade. ;) 2.0.4 will be out in days. Recommend you upgrade then as there are significant security issues that are resolved in it that affects all previous versions of WP.

  6. HART (1-800-HART) 27 July 2006 at 3:29 pm #

    I’ve been slowly upgrading all my sites. The ones with the most plugins takes the longest. PS.. can you edit the code for URL #2 on the 12:39 post for Jonic? Needs

  7. HART (1-800-HART) 27 July 2006 at 3:29 pm #

    I’ve been slowly upgrading all my sites. The ones with the most plugins takes the longest. PS.. can you edit the code for URL #2 on the 12:39 post for Jonic? Needs

  8. HART (1-800-HART) 27 July 2006 at 3:29 pm #

    I’ve been slowly upgrading all my sites. The ones with the most plugins takes the longest. PS.. can you edit the code for URL #2 on the 12:39 post for Jonic? Needs

  9. HART (1-800-HART) 27 July 2006 at 3:29 pm #

    I’ve been slowly upgrading all my sites. The ones with the most plugins takes the longest. PS.. can you edit the code for URL #2 on the 12:39 post for Jonic? Needs

  10. HART (1-800-HART) 27 July 2006 at 3:29 pm #

    I’ve been slowly upgrading all my sites. The ones with the most plugins takes the longest. PS.. can you edit the code for URL #2 on the 12:39 post for Jonic? Needs

  11. Rick 31 July 2006 at 7:57 am #

    This is a cool idea. But it is not immediately obvious from the name what the conversation view is. And, whatever view you’re in, the little bit of explanatory text below the graphics stays stuck on explaining the standard view.

  12. Aaron 31 July 2006 at 8:28 am #

    Oops, thanks, Rick. Will get that description text working. Hadn’t realized it wasn’t working…

  13. Aaron 31 July 2006 at 8:30 am #

    Rick – Actually, the sticky text is working. What browser are you using?

  14. Rick 31 July 2006 at 7:57 am #

    This is a cool idea. But it is not immediately obvious from the name what the conversation view is. And, whatever view you’re in, the little bit of explanatory text below the graphics stays stuck on explaining the standard view.

  15. Rick 31 July 2006 at 7:57 am #

    This is a cool idea. But it is not immediately obvious from the name what the conversation view is. And, whatever view you’re in, the little bit of explanatory text below the graphics stays stuck on explaining the standard view.

  16. Rick 31 July 2006 at 7:57 am #

    This is a cool idea. But it is not immediately obvious from the name what the conversation view is. And, whatever view you’re in, the little bit of explanatory text below the graphics stays stuck on explaining the standard view.

  17. Rick 31 July 2006 at 7:57 am #

    This is a cool idea. But it is not immediately obvious from the name what the conversation view is. And, whatever view you’re in, the little bit of explanatory text below the graphics stays stuck on explaining the standard view.

  18. Rick 31 July 2006 at 7:57 am #

    This is a cool idea. But it is not immediately obvious from the name what the conversation view is. And, whatever view you’re in, the little bit of explanatory text below the graphics stays stuck on explaining the standard view.

  19. Aaron 31 July 2006 at 8:28 am #

    Oops, thanks, Rick. Will get that description text working. Hadn’t realized it wasn’t working…

  20. Aaron 31 July 2006 at 8:28 am #

    Oops, thanks, Rick. Will get that description text working. Hadn’t realized it wasn’t working…

  21. Aaron 31 July 2006 at 8:28 am #

    Oops, thanks, Rick. Will get that description text working. Hadn’t realized it wasn’t working…

  22. Aaron 31 July 2006 at 8:28 am #

    Oops, thanks, Rick. Will get that description text working. Hadn’t realized it wasn’t working…

  23. Aaron 31 July 2006 at 8:28 am #

    Oops, thanks, Rick. Will get that description text working. Hadn’t realized it wasn’t working…

  24. Aaron 31 July 2006 at 8:30 am #

    Rick – Actually, the sticky text is working. What browser are you using?

  25. Aaron 31 July 2006 at 8:30 am #

    Rick – Actually, the sticky text is working. What browser are you using?

  26. Aaron 31 July 2006 at 8:30 am #

    Rick – Actually, the sticky text is working. What browser are you using?

  27. Aaron 31 July 2006 at 8:30 am #

    Rick – Actually, the sticky text is working. What browser are you using?

  28. Aaron 31 July 2006 at 8:30 am #

    Rick – Actually, the sticky text is working. What browser are you using?

  29. Rick 1 August 2006 at 9:44 pm #

    Strange. I tried it in Safari and Firefox, both on Mac OS X 10.4 and got the same problem. But now I’ve tried it in Camino, Safari, and Firefox, and it works fine. I do think it would be nice to have pop-up text (or whatever you call it), where the explanation appears just by hovering rather than having to try it out before getting an explanation of what it is.

    Also, in the Conversation view, “receive” is misspelt!

  30. Rick 1 August 2006 at 9:44 pm #

    Strange. I tried it in Safari and Firefox, both on Mac OS X 10.4 and got the same problem. But now I’ve tried it in Camino, Safari, and Firefox, and it works fine. I do think it would be nice to have pop-up text (or whatever you call it), where the explanation appears just by hovering rather than having to try it out before getting an explanation of what it is.

    Also, in the Conversation view, “receive” is misspelt!

  31. Rick 1 August 2006 at 9:44 pm #

    Strange. I tried it in Safari and Firefox, both on Mac OS X 10.4 and got the same problem. But now I’ve tried it in Camino, Safari, and Firefox, and it works fine. I do think it would be nice to have pop-up text (or whatever you call it), where the explanation appears just by hovering rather than having to try it out before getting an explanation of what it is.

    Also, in the Conversation view, “receive” is misspelt!

  32. Rick 1 August 2006 at 9:44 pm #

    Strange. I tried it in Safari and Firefox, both on Mac OS X 10.4 and got the same problem. But now I’ve tried it in Camino, Safari, and Firefox, and it works fine. I do think it would be nice to have pop-up text (or whatever you call it), where the explanation appears just by hovering rather than having to try it out before getting an explanation of what it is.

    Also, in the Conversation view, “receive” is misspelt!

  33. Rick 1 August 2006 at 9:44 pm #

    Strange. I tried it in Safari and Firefox, both on Mac OS X 10.4 and got the same problem. But now I’ve tried it in Camino, Safari, and Firefox, and it works fine. I do think it would be nice to have pop-up text (or whatever you call it), where the explanation appears just by hovering rather than having to try it out before getting an explanation of what it is.

    Also, in the Conversation view, “receive” is misspelt!

  34. Rick 1 August 2006 at 9:44 pm #

    Strange. I tried it in Safari and Firefox, both on Mac OS X 10.4 and got the same problem. But now I’ve tried it in Camino, Safari, and Firefox, and it works fine. I do think it would be nice to have pop-up text (or whatever you call it), where the explanation appears just by hovering rather than having to try it out before getting an explanation of what it is.

    Also, in the Conversation view, “receive” is misspelt!

  35. Vinnie 3 August 2006 at 9:48 am #

    I hate Trebuchet for long passages of text (just a personal thing I guess) but otherwise it looks awesome :)

  36. Vinnie 3 August 2006 at 9:48 am #

    I hate Trebuchet for long passages of text (just a personal thing I guess) but otherwise it looks awesome :)

  37. Vinnie 3 August 2006 at 9:48 am #

    I hate Trebuchet for long passages of text (just a personal thing I guess) but otherwise it looks awesome :)

  38. Vinnie 3 August 2006 at 9:48 am #

    I hate Trebuchet for long passages of text (just a personal thing I guess) but otherwise it looks awesome :)

  39. Vinnie 3 August 2006 at 9:48 am #

    I hate Trebuchet for long passages of text (just a personal thing I guess) but otherwise it looks awesome :)

  40. Vinnie 3 August 2006 at 9:48 am #

    I hate Trebuchet for long passages of text (just a personal thing I guess) but otherwise it looks awesome :)


Trackbacks/Pingbacks.

  1. Technosailor Redesigns + Restructures (and So Will blogHelper) | blogHelper - 24. Jul, 2006

    [...] After two weeks of labour, Aaron Brazell has completed the redesign of Technosailor – with key restructuring (or rather, re-architecturing) having taken place. Two new “views” have been implemented to supplement the current reverse chronological blog “view”. They are the Conversation view where recently commented posts float to the top, and the Best Of view which Aaron fills with posts that he feels to be the best he’s written. [...]

  2. Weblog Tools Collection » Restructured Blog? - 25. Jul, 2006

    [...] Restructured Blog? Very interesting set of links on how the present chronological structure of blogs might be robbing bloggers of valuable (and returning) readers. If you have not read of Chris Pearson yet or are not subscribed to his blog, here is your chance. Has anyone come up with a nuveau structured theme yet?   Related Posts from the Past: [...]

  3. Throw Away my blog. I’m Starting Over. » Technology, Blogging and New Media - 25. Jul, 2006

    [...] Worried Less About Design – I know this sounds ironic since I just launched a new theme yesterday, but design is overrated. I watch some blogs who change themes on a weekly basis and I wonder why. I used to do this too, but readers like consistency and changing themes is mildly disorienting. It’s bad behavior, really. Secondly, I have more RSS readers now than I do regular web readers. Which means it doesn’t really matter what my design looks like to them. [...]

  4. links for 2006-07-26 § No Categories - 26. Jul, 2006

    [...] But, it doesn’t act like a blog! Why are blogs ALWAYS structured in reverse-chronological order? Is there a better way to do it? (tags: technology blogging new+media) [...]

  5. doctorvee » The structure of blogs - 01. Aug, 2006

    [...] So, what are the other ways of presenting your blog? Technosailor offers visitors three different blog “views”. One — ‘The Current’ — is the standard style that we’re all used to, with the latest posts appearing at the top. But the other two are much more interesting. [...]

  6. blogHelper Redesign Complete (or At Least, I Hope So) | blogHelper - 03. Aug, 2006

    [...] Like Technosailor, a revamp of blog architecture has also occured – though “revamp” may be too strong a word. Instead of replacing view modes, I’ve merely supplemented the traditional reverse chronological view mode with another three and a half new views. I have no intention of allowing users to set these supplemental views as default modes, at least not in the near future. [...]

  7. blogHelper II Design Notes and Tips | blogHelper - 04. Aug, 2006

    [...] Just like Aaron Brazell at Technosailor, one of the first things I wanted to ensure was that this layout would be optimised for 1024×768 users because my stats show that around 73% of my readers have their monitor resolutions set at this value. Yet, I didn’t want to lose support for 800×600 users (15%) either. So, I opted to go with an elastic design (slightly different from fluid-width designs). This means that the layout will scale according to the size of your screen, up to a maximum and minimum width. In implementing the elastic design, I went with Roger Johansson’s technique as described at 456 Berea Street, where no minimum width was set. By the way, the technique is mostly cross-browser compatible, though a hack had to be used for Internet Explorer (IE) users. [...]

  8. Podcast 2006.4: Aaron Brazell & WordCamp 2006, Part 1 at The Blog Herald - 12. Aug, 2006

    [...] Technosailor: Blog architecture [...]

  9. 5 Reasons Not to Use WordPress As a CMS | blogHelper - 27. Aug, 2006

    [...] (Overly) Single Blog-centricAs said earlier, WP was meant to power blogs, so a lot of its features are optimised towards it. It’s hard to move away from a reverse chronological order post listing – meaning no alphabetical order, author-based order, etc., unless you use undocumented posts_* filters (and still have to hack around a bit more), or query your database to draw all your posts and sort them via PHP (it’s a pain for you and your server, trust me, especially since a lot of existing template tags, e.g. the_permalink(), may break in the process). [...]

  10. 5 Ragioni per non usare WordPress come un CMS » Studio404 Blog - 25. Sep, 2006

    [...] (Soprattutto) Blog-centrico Come ho già detto prima, WP è stato realizzato per i blog e per questo molte delle sue funzioni sono ottimizzate per questo scopo. E’ difficile passare da un ordine cronologico inverso – cioè da un ordine non alfabetico o per autore eccetera, senza usare filtri relativi agli articoli che non sono nemmeno documentati e che spesso necessitano di ulteriori hack. E allo stesso modo, effettuare query al database per ottenere tutti gli articoli e poi ordinarli tramite PHP. Questo è un lavoro pesante sia per te, che per il lavoro del server, credimi, specialmente perché diversi tag di template possono poi non funzionare. [...]

  11. WordPress Italy » Blog Archive » 5 Ragioni per Non usare WordPress come un CMS - 27. Sep, 2006

    [...] WP è (soprattutto) Blog-centrico Come ho già detto prima, WP è stato realizzato per i blog e per questo molte delle sue funzioni sono ottimizzate per questo scopo. E’ difficile passare da un ordine cronologico inverso – cioè da un ordine non alfabetico o per autore eccetera, senza usare filtri relativi agli articoli che non sono nemmeno documentati e che spesso necessitano di ulteriori hack. E allo stesso modo, effettuare query al database per ottenere tutti gli articoli e poi ordinarli tramite PHP. Questo è un lavoro pesante sia per te, che per il lavoro del server, credimi, specialmente perché diversi tag di template possono poi non funzionare. [...]