You want to build a website? Go ahead. Any monkey with a computer connected to the internet and notepad can create a website. Everything else is a matter of scale.

Yesterday I had a conversation on IRC, which ultimately went nowhere (as a lot of these conversations have done in the past over there), so I thought I’d explain the reason for revisiting the branding, website, documentation aspects of the Habari project and why I feel that ultimately it’s hurting the development of the software.

Design

Although much of design is thought of as subjective, obviously it's not all subjective. There are rules that you can abide by, or completely ignore. The thing is, unlike code, if you don't design it 'correctly' it's not going break and give you back an error. The error isn't immediate rather it is one the appears over the long term. What it will do is fragment your target audience, or detract them from coming back, or sticking around long enough to see if you're worth the effort.

Habari has been going on for nearly 3 years now and while it seemed ok in the first few years for the software to have a less than adequate branding, right now I think it’s hurting the exposure of the software to invite new people. Maybe I’m wrong, but from looking around in the community areas, forum, IRC and mailing list and how active those are, as opposed to how active they could be, I don’t think I’m far off.

The issue here is that critical mass hasn’t happened, nor is a uniform infrastructure in place to allow it to flourish. And while some might think that these things aren’t important, I beg to differ. If you’re happy with the software doing what it does right now, and don’t want it to improve, then fine, there’s version 0.63 blog off; those that want to enhance the software and the blogging experiences of Habari, read on.

Free

The problem you see is that there are quite a few different solutions out there for anyone to use. These alternative solutions are all free, they're generally pretty mature in features, have decent documentation, and have a community (with varying degrees of success).

It’s not like going Habari, means you get a cheaper product. You get other things with Habari, which unfortunately have not been flaunted properly, because well, they haven’t been flaunted at all. Again the devil is in the detail.

New Blood

So what's the problem you ask? Well, the real problem here is that by not attracting a larger user base, you're also detracting from new blood coming into the doors. This then reduces the amount of developers available to submit patches, to create plugins, to create themes, to push the general boundaries of the software. It's left on the shoulders of an able few, and so the software takes more and more time to move forward, often putting more undue strain on the existing developers, which ultimately isn't healthy for the general future of the software.

Solution

And you're solution is what? A new logo?

It's the start of the solution. The actual solution requires attack from several different directions. The things that I think need to be considered are:

1. Branding

2. Website

3. Documentation

1. Branding

Branding can be used to provide awareness back to the software. There are enough different solutions out there, which means Habari needs to distinguish itself somehow. Having a beautiful logo will entice people to put it onto their sites as a badge of pride and thus provide more widespread awareness back to the software. This of course brings up the whole subjective nature of what makes a beautiful logo. A good logo is memorable and should reflect the values/ideology of that which it is representing. It doesn't need to SHOUT it's raison d'etre. I've done my part with regards to this so I'll move on.

Branding isn’t only a logo. Thankfully the admin panel and the code itself has already defined these aspects. Elegance. Simplicity. Modern. Black. Grey. Inventive. ‘Out of the way’. All words to help better define the Habari branding. All elements which should be extended to the rest of the Habari presence online.

2. Website

Which brings us to the website. This is both our best and worst tool at the moment. When someone types in Habari in google or clicks on any one of the plethora of CMS demo sites, they are taken to the habariproject.org website. That is their first habari experience (after the name).

While you can’t be something to everyone, the website should at the very least try and address the various userbases: hobbyist, developer, designer.

The real shame of it (which is why I’m writing this) is that the site, does the software base a HUGE disfavour. The software and admin is better than that. It deserves better than that. Many times depending on how professionally put together a website appears it will attract or drive away potential users.

At the moment the page doesn’t do a good job of conveying what makes Habari special and better than the other solutions. It doesn’t distinguish itself.

3. Documentation

The importance of this cannot be overstated. The problem is, you need a larger user base in order to tackle this. The current documentation is written for developers. The complete novice, or neophyte like myself won't be able to understand what's going on most of the time. There is a way to writing good documentation and we need to address this as well. I have a few ideas with regards to this as well (I've done this within the company I work for).

Remaining Questions

How do we entice the young aspiring developers looking to gain some experience to come to us? How do we get the developer who is more familiar with WordPress or Textpattern? How do you get the web designer, who wants a more elegant solution (there's that word again)? While some of these questions are somewhat answered by the current website, again I feel they're not presented in the correct manner, but that's the next post.

I don’t have the power to enforce said changes, so I’ll talk and present my ideas on this site; if they’re employed, then that’s fantastic; but in a year’s time when we’re looking at the same general user base (having not gained much further traction) then maybe some of this will become more important. If not I’d happily eat some claim chowder.