So now that the plugins are working on the site, I’ve been able to get the archives plugin working, in the new Archives page. Still needs a lot of work to unify that look, but it’s nice to see all my posts over the years in one place. Definitely a slow down in the last year or so.
Well I just upgraded to the latest Habari developer preview release. This thing has been a long time coming. I’ve not played around with it too much, but it does feel much snappier. Upgrading has been a pretty damn easy process, and the way I’ve set it up, all future upgrades will be just as easy as well - using SSH.
I’m going to be posting a whole bunch of stuff about this, because I really think it’s good for people that are complete n00bs (like myself) to get stuck into this, as it’ll make the general process so much less time consuming.
So Owen’s responded to a few things that I’d written. I knew it was coming, and I knew it would be a big one, so true to form the man’s gotten back to me.
To be clear, although I didn’t voice it at the time, one of the reasons why I actually decided to move over to WordPress a while back was in fact when it transpired that Owen might leave the project (I don’t know the exact details, but it seems a community member was maybe hurting more than helping). In any case, Habari without Owen is a much poorer place. Not to take anything away from others who tirelessly contributed to the code, but he’s amassed probably three times as much commits as the next guy (roughly speaking) and generally leads the way - so I listen when he’s got something to say because I respect him enough because he spends the time to explain himself properly. Forget the fact that we don’t agree on everything, I think it’s clear we both want the software to move in the right direction.
I would love to replace the logo with something better. But something decidedly, unarguably better.
That’s the biggest problem. Who’s deciding which is unarguably better. I can argue that the question mark is brilliant and the non-descript H is rubbish till the cows come in, as I’m sure others can argue the direct opposite. The point is, it’s your opinion against someone elses. The frame work is not there for moving it forward either. We’re not going to strike lightning in a bottle, nor do I think that I can make something that is universally liked by everyone. Fuck me, that’s pretty much impossible to do. For everyone that thinks the Nike swoosh is an icon, you’ve got others proclaiming that it’s completely pointless.
The point is taking where we currently are and moving forward. Otherwise we end up hurting things more and ultimately not achieving anything.
My suggestion? Elect a sub-group of people to huddle somewhere, create a plan, build something usable in a staging place, and then report back to the community for review. They take comments, re-huddle, and iterate until either everyone loves it, or there's no budging by one side or another. And at that point, the community defaults and uses what they've built.
I’ve created my logo. So if anything, I’m happy if I was the one making the decisions. My thought process is clear to me. The logo is out there for anyone to pick at as they please. I had an idea, I put it forward. It didn’t take me too long, hell writing up the previous 5 Habari posts probably took me longer to be honest. Like I said, if anything, I’ve got a nice t-shirt design.
I’m not adverse to exploring the issue further with a task force, hell I think it’s a great idea but ultimately I want to know that our work will be accepted, or voted upon. I want to know the structure, because the exercise will take more time out of me and honestly I don’t want to waste my time - which I’m sure you can appreciate.
The next question that should be raised is, does that then get used instantly? According to Owen, that shouldn’t be the case. It should be reviewed by the rest of the community, lather rinse repeat. This can work, after a fashion. I propose that this is done in a finite number of stages. When we design a building (I’m a building services engineer), the design process is broken down into 4 distinct stages (at least from an engineering POV). Concept, Scheme, Tender, Construction. In a similar fashion, we can also break it down into a few stages.
Concept - Ideas about what it could be are thrown on the table. The question mark, the capital H, the doorbell etc. At this stage it is important NOT to rubbish any ideas. This is to create as many ideas as is possible. No idea is off limits.
Scheme - The ideas with more legs are weeded out. This is going to be time consuming, because ultimately it is important to come up with one or two ideas options which can be further pursued. The point here is reduce the number of options to a manageable few that can be detailed further.
Tender - The few options that are thought to be in contention are whittled down to one. Maybe the execution isn't perfect but ultimately it's an idea that everyone is behind. The general thought process is there.
Construction - We build the logo based on the finally selected option. The detail is put in here, and the various elements are presented to be used. In the software, on the website, as badges etc. Used in 'press' releases. Whatever.
We report back at every stage. Any thoughts are processed then and then we move on. The other thing that is important is to have a proper timeline for all of this. Otherwise it’ll meander endlessly. Therefore I propose 1 month for each stage. Gives people enough time to consider, think about things, review, reflect, write emails/responses/posts if they have an issues concerns ideas.
We don’t jump back several stages. The rest of the community had the opportunity to review and present their ideas in the given timeframe. Inaction is not allowing progress which as I’ve explained has a negative affect on the software base itself.
If anything it’ll be an interesting exercise to see if design by commitee works on the internet and in an open source project. Afterall, how do you think all those buildings that you live and work in were designed? By the choices of one person? Don’t be silly.
I get the feeling that when you're done tearing the thing down, assuming you have any energy left afterwards, you might actually do something. Am I right?
I hope so. Like I said, it’s not because I think this will raise my profile, or because I want to have the Habari logo as a notch in my design portfolio (I don’t even have one, although I keep meaning to create one). This is all being done to ensure the progression and future of the software (selfishly because I enjoy using it). I’m not going to let a few with myopic vision hinder PROGRESS dammit :).
So it seems I might have come across as being negative and I guess some have seen my last few posts as diatribes.
Just to be clear on something I’m genuinely not trying to be rude, I’m trying to build awareness because I can see a problem that I think will ultimately have an effect on the software and the developers themselves; which obviously I don’t want, because I enjoying using this software immensely and I want it to succeed. I don’t gain anything personally from doing this, except the satisfaction of giving something back.
I think the general consensus in Habariland is split with regards to my logo proposal:
Those who think the current logo is good and we don't need something new.
and those who like the 'idea' of the question mark, just not the current execution of the one I've presented.
Honestly, I can live with that; actually this can be considered as progress. Would it be useful to have a look at drawing a couple of other question marks? Would that be a rewarding or ultimately futile effort/exercise? Should i just carry on with the next task I’ve been working on (namely the website)? Would it actually be something to present for a vote by the community? Is there any point?
I ask only because I obviously want things to move in a positive direction to make the software better and to make the experience of using the software better.
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.
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.
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.
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:
Branding
Website
Documentation
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.
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.
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.
You don't need a designer. You need a marketeer.
That’s what my brother said to Yanni last week sometime when we were discussing his online radio station as he was lamenting that not many people were listening to his station. That got me thinking about Habari. It’s been going on for a while now, and yet I don’t feel like the software has hit a critical mass, which is a shame. I think there are several reasons for this, but I’ll start with the first part in trying to help the guys and gals move forward.
To be completely blunt, from an aesthetic POV it’s not terribly elegant and doesn’t really convey anything about the actual software, the community, etc. That eyesore has to be sorted out for the good of the software (I’ll be going into this in more detail in a future post). Rather than just bitch and moan about something, and not actually do anything about it, I thought I’d take up the challenge. The thing is I did attempt to do this 3 years ago, and I came up with this lovely collection:
Yeah, shut up. I can actually see my thought process, but I guess at the time I was more interested in making something that appealed to the people that had originally started the work (the original Cabal). Thankfully, now I’m just out to make a good logo, that people can use in a plethora of applications, is memorable as the Habari software and is nice enough for me to want to include said mark on my website as well.
Obviously the logo should reflect the software itself, which I have repeatedly been calling it elegant, both in code and in design.
Habari
What's the news?
Then I paused. Why the hell didn’t I think of this before? Habari may by definition be a noun, but it’s also a question. What’s the news? Habari is also the answer, a method to provide the news online. The simplest answers are sometimes staring you in the face. The logo should be the question mark. For some reason I instantly knew how that question mark was to look like, at least in my head, but first I thought I’d try seeing what it looks like with some typical typefaces, Helvetica, Gill Sans etc. This is what it looked like:
Convinced that the actual idea had legs and the more I thought about it the more I was convinced that this as an idea is a good one I started sketching. The thing is I didn’t need to sketch for long, because like I said the second I had the idea, the logo was fully formed in my mind. There would be no harsh lines. The reason for this is because that’s not what Habari is about. It’s about elegance, not sharpness. It does things slightly differently than other to smooth your general experience (this is evident from the installer through to the admin panel and beyond).
So here’s my proposal for the new Habari logo:
I’ve also included this set of iterations, which show the logo in both dark and in light colours, on white and on dark backgrounds. The logo remains distinct in all these incarnations.
This next set shows the logo at different sizes: 100px, 75px, 50px, 25px and 16px - click here for the full size of the image.
There have been other attempts at looking at this in the past, all of which have failed, so I don’t think that this time is going to be any different, because it’s a very touchy subject (which is why it’s not moved forward in 3 years). I don’t really expect anything from this exercise to be honest, except that I for one want to at least know that I tried to help in this regard and gave a viable (and hopefully useful) alternative.
And if anything, it would make an awesome t-shirt as well:
So now that we’ve got ourselves a kick ass logo, now would be a good time to make some badges so that everyone can put them on their websites and you know, spread the word.
In this set you’ll also find a few with Habari written in them.
See how that logo gets integrated? The font used is Gill Sans, which is one of my favourite fonts - you can see it in use on this site. The reason I think it works here is because it’s rounded so it retains an element associated with the logo (the playful nature of the logo), and yet bold and modern (like the software). The package contains:
PNG - Light grey on white background
PNG - Dark grey on light grey background
PNG - White on dark grey background
EPS - Vector for you to customise as you wish
PNG - Dark grey on light grey background
PNG - Light grey on dark grey background
PNG - White on dark grey background
PNG - White on light grey background
These will also find a permenant home at www.brokenkode.com/habari .
One of my absolute favourite plugins on Habari is the Publish Quote plugin written by Michael. The plugin has done well by me for like over a year, but in my mind there is some room for slight improvement in the way it operates. Habari does a great job of staying out of your way (as I found out the hard way) and I feel that this plugin is really a direct extension of that, which will make it even easier for you to actually publish your thoughts quicker and faster, ultimately making you blog more.
Currently the plugin works by taking you back to main admin panel with all the various fields filled in (according to your option preferences). There’s nothing fundamentally wrong with this approach. As long as you’re logged in, you have no problems (and seeing as I use the persistence of memory plugin my Scott, I’m ok on that front as well).
The ‘new’ Publish quote plugin would operate in a similar fashion. Clicking the bookmarklet would provide a drop down card which would sit above the page. The card would look like this:
The card has rounded corners (to be consistent with the admin panel) and also includes the slightly greyed rounded box in the top left hand corner around the title of the plugin (more on this below).
After all the whole point of this is to communicate your thoughts and ideas as easily as possible in an enjoyable fashion.
Lets turn our attention to the main menu in Habari. As I mentioned before there has to be a better way than the current method. The reasoning for the current menu is simple, once you start adding all the menu items (including those provided by the various plugin) the list becoming very long indeed. Without any plugin menus this is what is currently there (including one of the expanded menu version):
And here’s that menu with one of the side menus popping out:
From my personal use, I only need 8 menu items in total:
New Entry
New Page
Manage
Comments
Dashboard
Plugins
Options
Logout
For me everything else is completely superflous, or at least it’s bloody rare for me to even go there, like once a year if that (I don’t think I’ve ever gone to the logs and groups menu for example). As I said that’s only because of the way I choose to use Habari. Other users might feel like they want something a bit different, and this type of functionality would allow
The other aspect of this Menu plugin that would also hopefully enhance the experience, would be bringing the shortcut numbers back. In the options menu we would also provide an option to assign the menu option with a keyboard shortcut to a menu item. This way we’d get back to a more streamlined workflow, which is slightly hindered by an additional keyboard stroke (at least in my eyes it is).
For those who know me from my professional life (I’m a Chartered Engineer), know what a complete filing freak I am. All graduates that have helped me out, or that I’ve had anything to do with their training have gone through an induction with regards to how to file things properly. It’s a MASSIVE bug bear with me.
When I had that moment of madness and I moved over to WordPress, what struck me was that Habari’s elegance doesn’t extend to just the admin panel. In Habari it extends to the filing structure, which I really want to shine a bit of a spotlight on, only because I think it’s not generally discussed and I think that the developers deserve mad props for building this elegance in.
When you download a copy of Habari and you open your folder, you’re presented with the following files and folders:
Let’s compare some of the other people:
There are a couple of things to take from the above. The first is the number of files without folders. In Habari, this is a total of 3, in WordPress it’s 23, in Textpattern it’s 4, while in Chyrp it’s 5.
The second thing to pay close attention to is the names chosen for these folders. I know which I feel is the clearest filing structure of those above.
In looking around the Habari admin panel I’ve got to thinking which areas are important to me in the way that I use the software and how to take care of those pesky little design issues which I see as glaring mistakes. These are the areas that I feel could use a little bit of design TLC, which basically will give the software that added bit of polish and maintain it’s elegance.
I’m currently in the process of learning PHP, so hopefully in a few month’s time I’ll have hopefully created the plugin to deal with these few issues. If they’re seen as a good idea, then maybe they can be included into the core, but I’m more interested in getting the software to do what I personally would like it to do, good ideas often times find their way back up the trunk. If someone wants to jump in now, I’m not going to stop you, and will gladly help where I can.
Solution: This information should be collected into another card that sits with the rest of the cards and can be moved around in the same fashion to suit the person’s preferences.
Solution: I would go even more minimalist. As an everyday user, I don’t actually need to have most of these options available on my screen. I don’t need to have:
Logs
Theme
Users
Import
Groups
My Profile
Personally, the only secondary options that I would like to have are the Options and Plugins (secondary options being New, Manage, Comments and Tags). Other people might have a different approach, but again I would probably argue that every person has got options in that menu which they rarely use.
To that end, I would reinstate the original design of having a sub menu present inline of the main menu item. Within the ‘Option’ page there would be an additional section which would allow the end user to ‘hide’ some of the menu items. The only backend menu items that would be present as a default would be the Dashboard, Options and Logout. You would then reduce the length by 6 lines deep.
Earlier this month I moved this blog back over to WordPress in an act of madness. I hated it and did little blogging in that time. In considering why I hated the experience at WordPress so much, I came upon an interesting parallel. Habari is to WordPress what Apple is to Microsoft.
One of the things that can be said about Apple when compared to Microsoft is that Apple provides a more elegant computing experience that has been better thought out. In a similar fashion Habari is by far the more elegant product where the details have been sweated out and the experience has been better considered.
As a simple example when you install WP you get a random password in your email box and then the second you log into the panel you get a message asking you to change your password. Why didn’t you let me choose a password during the installation process?
Meanwhile on Habari, the installation is all done on the same page, you insert your preferred password right there.
As another example once you’ve logged into WordPress you’re bomobarded with this clusterfuck of items - TMI (too much information). Yes, i know you can remove most of that stuff (but this is all feeding into my analogy). These items aren’t necessary, they’re added first and you are asked to remove them. It’s like when you buy yourself a Dell PC and get a whole bunch of crapware installed on it, which you can remove (most of the time).
Habari doesn’t have that shit to begin with. These items have not been added from the outset. These things have been considered. And who else do we know that doesn’t like superflous stuff cluttering your view and generally getting in your way? These are just a couple of examples which I might expand upon, because the above is basically the tip of the iceberg.
These are subtle differences but important I think in the final assessment, afterall the devil is in the details.
After a moment of pure madness, I went back to WordPress, only to find that actually the creature comforts that I had become accustomed to in Habari were not present. It had such a detrimental effect on me that I could even post small links. The bookmarklets didn’t work, the thing felt heavy and I couldn’t wrap my head around the various elements of the code that had passed me by.
I’ll be writing more about Habari in the coming months as there definitely is a lot of work being done, but it just needs a bit of, consolidation of sorts.
If you’re reading this in your feed reader, then have a look at the site, which looks a little bit different, as I’ve also updated to version 9.
What’s the reason for going back to WordPress? Simply the plugins and documentation available to me to actually do what I need to get done. Yes I could called on the Habari community, but I just want to get on with things. Trying to write something like P2 for Habari is definitely out of my scope of knowledge. I’m not a developer. I’m not even a web designer. This is something of a hobby that I enjoy playing around with. But it should get in my way, and unfortunately due to my inadequacies as a developer Habari was getting in my way. I really really hope that in the future I’ll be able to make a proper and permenant jump over to Habari, but now is not the time (I did attempt it for a year, but my site looked more like it was created in 2006 rather than in 2009).
I am more than happy to play around with this and make it work for me, slowly moulding it and shaping it to what I want it to do, but writing this from scratch would be too much of a pain in my ass.
So here it is, comments are back online (for now) and I’m sure there is going to be a load more things to come in the not too distant future.
It’s been nearly 4 1/2 years since comments were officially not part of this site. Back then it was because I couldn’t actually host them on my own site, until of course I moved to WordPress and during the blogging revolution of the early naughties. So what’s changed? Twitter and Facebook. Both of which have brought the internet to the world that hid themselves from it, but they’ve practically killed the blogosphere, or at least how it used to operate.
The funny thing is turning them off was on the cards for a while now. I’ve noticed this downturn for about a year now (probably a few months before I even moved to Habari as my blogging engine of choice).
Does it upset me? I guess it’s a different kind of change. While sometimes I like twitter, there’s too much noise for me on there. Also the fact that everyone only speaks in soundbytes does annoy me. I can’t read people’s thoughts about things because they’re limited and effectively people’s voices on the internet are silenced.
In the meantime I’ll be here writing more than 140 characters and hopefully sharing some good links from around the net. If you want to comment on something, drop me an email or you know…send me reply on twitter (maybe I’ll even integrate that twitter reply thing that Michael is attempting at the moment).
TweetBacks - Great little plugin for WordPress (that will hopefully be making it’s way over to Habari) that bring Tweetbacks. Think of them as trackbacks only made of tweets.
Today I was reminded that you cannot force design. You cannot force creativity. While thinking of something else the inspiration will strike. From my point of view, whenever I create anything I can actually see the final product in my mind. Sometimes depending on whatever it is that I am doing I will see this picture clearly and I have the necessary tools and skills to achieve that vision, othertimes I can see only my shortcomings…this is probably the norm to be honest.
The site’s design has been building slowly, organically as I got used to the Habari codebase and also what I wanted to do. I pretty much guarantee that the actual colours wil change, however I’ve got an idea in my head that if executed properly could be pretty good fun for me to see and also could be a good note to stop the redesigning of the site for a good long while.
Habari Article on Linux.com - Slowly but surely the revolution will begin.
Expect breakages, spills and loads of stupid things to go on the site, for a long while, until I get my freak on and actually get to the bottom of where-ever it is that I want to go. Either way I’m hoping to make something to move past my cables design from a few years back.
Edit 1 - So the colour scheme in my mind has settled down a little. There are three more base colours to come, but really that’s only going to be in full view once I’ve sorted out the artwork that is going to be pasted all over this site (from which those three base colours will come from). I’m still playing around with the typography and trying to see if I’ve missed something fundamental in the last 6 months that I’ve been out of the game. More about that laters I guess.
Christian wrote a little post asking why the Habari community was snubbed in the recent Smashing Magazine 10 Weblog Engines Reviewed post.
Why was Habari not included in this list? Well it was included in an honourable list. Instead though they included Joomla and Drupal. All very good applications in their own right, but far too bloated to be considered weblog engines (they’re designed for bigger sites are they not?).
In any case, I feel that the reason why Habari wasn’t included in here is a collection of things, but it is telling. While I wouldn’t go so far and say that Smashing Magazine in the authority of the internet Zeitgeist, I will say that they generally put a lot of effort into their posts and do a certain amount of research, so their not so much dismisal but rather short billing is indicative of where Habari stands right now. The problem is that I don’t think that Habari, the community or software is to blame here; rather I feel it has something to do with the net landscape as we are right now.
You could say that Habari is still pretty young in it’s cycle, however it’s a HELL of a lot more developed than the bit of software called WordPress was when I started using it (version 0.6 I believe). Back then WordPress didn’t have ANY themes. The plugin library was in the single most infant state you could imagine (if you compare it to now). The less we talk about the interface the better (that ship is stll a rudderless pile of shit as they change it more for version 2.7 if the latest betas are to go by, and believe me I don’t care enough to go there anyway). I don’t think the reasons for the lack of credibility can be attributed to the software’s limitations, because if you’re looking for something to post a blog, and enhance your site with any one of the currently available plugins, Habari is a pretty solid foundation that is only moving forward, moving into the future, because honestly all of those other ones that are on the Smashing Magazine post feel like the past.
So what is missing? Blogs are now a standard part of the net landscape. Open source projects are a dime a dozen (hell that list isn’t exhaustive by any stretch of the imagination, since it doesn’t include Habari or Chryp, to name a couple). Blogs are not this new and exciting medium that they were 4 years ago. People know about them and have had one at some point in their lives, even the completely tech neophytes out there will have dabbled. The options to create something online are a lot larger than before.
The other thing is that Habari hasn’t had a catalyst that exploded the scene. There was no Moveable Type changing their license rubbish and now back again (or whatever). That was the push that WordPress needed, initially. Right now, work is being done on WordPress but honestly it feels more like a rudderless titanic. Then you’ve got Textpattern….seriously is the project still alive? A while back I heard of a Textpattern fork, not heard anything else about it since then, but then again I’ve not been actively seeking any information so they could have moved forward?
The thing is that to draw people in there has to be some form of marketing push. What I mean by that is the word of mouth about Habari really has to begin in full steam. The great thing is that people are starting to do this, slowly but surely. Michael is talking more about Habari, as is Owen and Chris. Remember those badges that lived on the side of blogs? Remember the ones for Firefox? The thing with those of course is that the actual image usually pretty distinctive. The firefox logo is extremely iconic. Something akin to this would help spread it out again. It could be a community push that al those actively running their sites on Habari should have the badge to wear proudly.
Clearly there are other things that need to be done, however as with the Habari motto, the word really needs to be spread in a number of ways which can only be a good thing for the software and the community.
After nearly 4 years running the Kode on WordPress, I’m making the jump and going to better pastures. The internet in general is not high on my priority list, however I love the Kode and want the best for it, WordPress has not been the best for it for many many moons, which is probably one of the many reasons that the site got a bit left by the wayside.
Expect a little bit of breakage, maybe even come back later for the new RSS feed (which I think will probably be http://brokenkode.com/atom/1), as I transition over to Habari. See you on the other side.
You know what I find the absolute weirdest thing in the world? I’ve got this Canon LiDe scanner right, got it something like 5 years ago and has served me pretty well in all those years. It’s not the best scanner in the world, but to be honest, based on the fact that most of my stuff is put on the web rather than in print, it’s not exactly the end of the world. The weird thing is that my scanner works right out of the box in Ubuntu. Don’t need to download any drivers, don’t need to mess around with anything, and it works quickly and perfectly. Obviously it’s not all roses right, my Ipod shuffle obviously doesn’t want to play nice with Ubuntu, even though the latest version of Banshee is the music player that I’ve been waiting for all my life. So many great little features have been added to the latest couple of versions since I played last with it. Yeah like that’s any good to me as my fekkin sound card that doesn’t work for toffee and keeps giving me trouble all the time.
So I get back on Windows (because it’s got Photoshop) and fekkin Apache has decided to stop bloody working through XAMPP, so I can’t honestly get any work done for Habari as doing it on a live server takes forever.
I did download the latest and greatest Oxygen icons onto Ubuntu and I’ve got to say they are definitely some of the nicest things I’ve seen in a good long while…shame I couldn’t get the latest version of the Crystal icons to fekkin install (lovely redesign by Everaldo btw), as those look great as well.
Obviously I’ve upset someone in computerland and they’re trying to punish me in every painfully frustrating way. Seriously it’s times like this that I think the magic bullet is getting myself a Mac. But then again everyone says that when all manner of software decides not to work right?
So I finally got around to doing some work on Habari this weekend, which was awesome. First time I actually used SVN and the guys and gals on the channel gave me a right grilling. Obviously I fucked things up the first time around but alas that’s ok, it’s all part of the experience. Below is the screenshot of what the current dashboard is currently looking like. It’s currently employing Blueprint version 0.5 which honestly has made my life soo easy in that I can actually concentrate on designing rather than setting up grids etc. Still LOADS of work to be done, but steadily this little project is coming along pretty nicely.
One thing that has me kind of stumped however is why the hell the tables appear differently? For some reason the height attribute for td element doesn’t work in Firefox. Anyone got any ideas what can be done about this?
The second official release of Habari, version 0.2 is out the door. Everyone has been working real hard, always with love, always with passion. One of the things that this release includes is the user manual which is included with the release. Yes, when you download the software, you’re downloading the manual as well. For the manual we’ve chosen to use the awesome Tiddlywiki for this purpose. Don’t be afraid get involved. Spread the Word!
Well it’s been a bit too long coming, but I think I’ve found a theme that I can get to grips with relatively easily. I’m going to be hacking Depo Clean, adding parts of Fauna and some K2 in for good measure. I had a look at Sandbox and I’ve got to say that I was pretty turned off by the function.php file that they’ve added in there. It just makes the markup so much more difficult to understand at first glance which is what made me keep looking for alternatives that just did the job cleanly. In any case Depo Clean probably best resembles what I’m aiming for in the end anyway so it helps that I like the markup as well. The next time I do this I’ll be converting this markup into something that can be used with Habari.
Interesting developments over at Six Apart. Lets dig up some of the things I said back in the day about this shall we. For all those in the dark, MT was the defacto CMS you would choose if you were in the market to get yourself a blog with comments setup on your server back in 2003-2004. Of course what happened was the Six Apart crew got a bit greedy at the time and all this free effort by the community was kind of slapped in their collective faces when they introduced the updated version 3.0 which was built off the backs of the community and sold back to them. The original pricing scheme was a complete farce but they revised it when they got the unexpected (erm yeah) response.
What this did was move all those people who were originally using MT to convert to an alternative. Some went to Textpattern, most went to WordPress.
3 years on, SA are now doing what they should have done way back for version 3 and maybe have kept some form of dominance. Currently however I feel it’s far too little too late. Do I give a shit about MT? Not really. I’m not interested in remembering how to write templates using MT-Tags and other bullshit. I’m not interested in revisiting the past. I will say however that the admin looks nice, and it’s also very cool that the actual engine dealing with that is the same as the one dealing with the blog itself, so I’m definitely going to bring that up with the Habari folk.
Ah yes, Habari, whatever happened to that initiative you might ask? Loads have been happening in the background but nothing massive for me to personally talk about. I’m sure once I get some more free time I’ll return to more active contribution and discussion, but I’ll leave that post for another day.
Let me start off by saying that Inksmith is what I view as my biggest online failure, after a fashion and this is what this particular post is about. Whenever I announce a project or something I usually deliver, notice I said whenever I announce a project. I may be a blabber mouth an I do get excited about things and have the urge to talk about them, however I never announce until I’m 100% certain I’m going to follow through (seriously if I didn’t do that I’d be writing this sort of shit all the time).
I might take some time to bring it forward (usually I take a lot longer that I could possibly want) however the fact of the matter remains that I will see things through. It seems that ever since the ‘announcement’ of Habari a few moons ago, some have brought up Inksmith as a way to bring discredit to Habari (at least the negative connotations that Inksmith is presented in infers this). It’s as though the fact that nothing moving forward on Inksmith is telling of stuff that might not happen on Habari, which honestly is the single most preposterous idea I’ve ever heard. These are two very very different things and I find those that mention them as though they’re linked in the same way done so as an act of ignorance/stupidity/lack of understanding etc. Here’s why.
The first fact brought forward is to understand what the two things actually were. Inksmith simply was an idea to create a community for bloggers. No this wasn’t a rip off on 9rules. I wasn’t creating a blog network but rather an area for bloggers to get around and be themselves. Oh sure there wasn’t really a central theme for us to bandy around, but what I wanted was a nice buzzing community that helped each other out and was open for people to get to know each other re our love for blogging. It wasn’t ground breaking and it wasn’t anything crazy, but it would have been fun and loads of the guys where well up for it. The best part of it all was the pictures on the coming soon site. I really liked the fact that we were all pissed off in those photos. It delivered what Inksmith was all about, angry people on the internet venting :).
Habari on the other hand is blogging software.
So where does the similarities lie you ask? As far as I can tell it’s the fact that some of the names attached to one project are now attached to another. So does this mean I’ve tarnished the credibility of the others on that list (since it was my idea)? Maybe and I guess they are the only ones I owe an apology to, because I didn’t deliver on my part of the bargain, so to everyone that was attached to the Inksmith project I apologise profusely. Let’s get something clear here, if I ask someone to be part of something I take their commitment seriously. I generally don’t like to waste ANYONE’S time as time for me is the most important commodity. So I genuinely feel bad about wasting those people’s time. We had some great discussions and it did prompt a lot of people on the internet to discuss the deal with being anonymous on the internet and using handles.
Why didn’t Inksmith take off? Because I didn’t have the energy to kick it off. 2006 was one of the toughest years on me from many many respects. In fact from May onwards I can definitely consider 2006 as one of the darkest times in my life from many angles. Which is actually reflected in my blog. What, you think that the dark motif was because I was joining in with the trend for darker sites at the time? No, Broken Kode is an extension of me and it reflects my mood in many cases. When my mood changes so to does the colours on my site, and the design itself in many respects.
So why didn’t I get Inksmith started? Honestly it came down to the amount of energy and enthusiasm I had to provide for the project, which after completing FOFR and Shuttle and 2 websites for clients and my on website and a bunch of illustrations I just didn’t have any more to give, until I was in Greece in October/November. At that point I had charged my batteries and I had decided that it was time for me to pull my finger out and build Inksmith all over again. For all the negative assholes that don’t believe me here’s the logo I created on the plane back to the UK:
So why did I stop that momentum? Simply put because the day I got back from the UK Chris had emailed me about Habari. In Habari I basically found another way to solve the problem that I wanted Inksmith to solve in the first place; the difference of course is that we’d have a central idea to gather around and that would be the software.
The community coming together around Habari is one I’m very proud to be a part of in the first instance. Final word to those that decide to put Inksmith in my face one more time, seriously try and do something constructive with your time, I know I am.
It’s been a truly exciting time for Habari on the design front (not that it’s not been exciting on the code front, but I can only really properly comment on all things design to be honest). Since the last time we talked, Michael has been a busy boy with absolutely everything under the sun. All these ideas have been filtering through the designs as we build towards a unified look for the administration panel.
Remember these mockups are just that mockups, we’re still meandering trying to sort things out, this is an open design process so things are going to change. Don’t think that what you see here is gospel and how it’s going to be, don’t be quoting me fekking Jakob in my face about usability and whatnot. These are the formation months, trust me we’re going through MANY MANY loops and discussions. So with that in mind let’s begin shall we.
Stage One:
Final Stage:
We’re still playing around with loads of things here. The header and footer are still up for discussion but the main ideas are there. We’re definitely going for the easiest installer award with this release.
Michael’s been pretty busy and he’s got his ideas regarding the media browser on ‘paper’. Once we’ve ironed out all the kinks and how it’s going to work I think it’ll be the most special media browser on any blogging platform.
We did have a great deal of interation of ideas between us on the logo. Work is still ongoing in this area and probably will be for a little while longer as we try and find ourselves the best fit for what the logo means to the community and how people will view us effectively.
Remember nothing is set, everything’s up for discussion. As always Spread the news!
This is the first (hopefully) weekly instalment of the comings and goings on in the Habari Design Community. As this was our first week ‘out’ it was obviously a pretty wild and exciting ride with an immense amount of interest from all people around the world. What’s fascinating to me is that the people at the table currently trying to shape the design aspect of Habari. We’ve got Michael and myself working on all things admin at the moment, with comments from the entire community. Bryan Veloso has joined the team and he’s going to be handling all the website related stuff (from main site to wiki design to whatever the hell else we can keep him busy with) and we have the truly talented Yoram who’s kindly offered to do the icons, so as far as I’m concerned we’re in pretty good shape regarding the graphical direction the project is going to have.
A great deal of work has been done in the logo department. However we're still not really decided on the direction we want to take as the current options on the table haven't been a unanimous 'HELL YES'. There are merits to all of them but I think with respect to the logo it's better to just wait for that one idea that jumps out at us and really makes us all smile rather than settling for a right here and right now solution. Here's a few examples of what are on the table:
A lot of work has gone into the installer as well. I'm not going to comment on the design of the installers, because that's out in the wild going through the motions.
We’re still hammering through these back and forth, but the idea is there, one click install, degradable JS that makes parts of the install appear as and when the previous section has been completed and verified.
Very minor tweaks going on here, except of course the colours. The pink is displayed for when you hover over the log out button.
More work going on this part. We've been having a lot of discussions regarding the number of buttons we should have. The subtle addition to these mockups is the slider for the tags (think increasing/decreasing the tags on display).
Remember nothing is set, everything’s up for discussion. As always Spread the news!
It’s been one hell of a couple of days since we first talked about the Habari project. There’s been a slew of reaction to the news all over the internet (go to the pingback section of that post) and to be honest it’s far exceeded all expectations I could have had because I honestly don’t have any. See I wasn’t completely sure how everyone would react over the news and therefore I was preparing myself for a little bit of a fight, in so much that we would have to prove the meritts of the software before we got people actually wanting to join and help build the community.
This in turn got me thinking to what all this meant and so I’m writing this post for several reasons. A couple of them is to dispell any rumours, a few others is to point everyone in the right direction should they want any more information, while others is to address concerns I’ve heard from people over the last couple of days.
There's been a lot of speculation as to why we're doing this. I'm not going to speak for the others (because they're doing a pretty good job of it themselves to be honest) but I'll tell you why I'm doing this. I've been talking to (read: boring) many of my offline friends with just how cool this is going to be. The first thing that they ask me is "Why the hell are you doing this to yourself? Why are you working for free again? Why are you spending your free time doing this?" I can only answer by saying that it's incredible fun to be part of an online community of like minded people who are trying to make one of my favourite pastimes (ie blogging and tinkering with my website) a more enjoyable experience. I love being involved in open source projects and this is without a doubt one of the biggest things I've ever been involved with.
When I first started looking for an alternative to Movable Type I had two options. The first was WordPress the other was Textpattern. I chose WordPress for the community. That community however has changed. It’s core has shifted into something different. The thing is though I can’t really say that this is the community’s fault. This shift actually can be attributed to something else. The fact of the matter is that WordPress developement has stagnated as far as the .org user is concerned.
The only explanation I can give is that this is because the WordPress development shifted it’s attention. Shifted from the .org section to the .com section. I’m not going to condem the guys for doing this, in fact in most cases I understand them doing this. However this move and shift hasn’t gone unnoticed and obviously a lot of energy flying about the WordPress community has either gone into the ether, ignored or shrugged aside. All these thousands of people out there that have contributed in the past feel as though they have been forsaken. That could be part of the reason why a great number of people genuinely got excited about the prospect of a new system, written from the ground up that might address questions. It’s all about the community. It’s all about the people that you interact with and that help you along your way.
What you think the latest release of ‘features’ on WordPress.org is a coincidence. It’s obvious (to me at least and this feature could have been in development for months, in which case I apologise) that this is a knee-jerk reaction to a situation that obviously has made them sit up and think about the situation. It’s not every day that several prominent developers (Robert, Owen, Michael), at the very least in the past otherwise they would not be in the credit box on wordpress.org, decide to leave and start something on their own; it’s a sign that something isn’t exactly right in the community. My absolute favourite one however is this one (I only saw this because it was lying in my referrer log), so yeah go and hammer that link and lets get it up there at the top :) lol.
Don't be silly. Nobody is trying to kill WP. We're not aiming to make software that is better than WordPress, we're trying to make software that is better than ALL blogging software out there. Lets be clear about this there are quite a large number of open source projects that allow you to do essentially the same thing. Their degree of complication obviously varies, however the fact remains that there are many alternatives. As it stands it's considered that WordPress is the best alternative that's available on the market. So it's obvious that people would think that we are in fact trying to create something that out does WP. Also many of us have come from a WordPress user base, however that doesn't mean other people from other backgrounds cannot join the fun. But would we really be getting involved and doing something if we didn't feel like there was a void to be filled? Room for one more solution that offered an alternative way of doing things? We're ultimately here because we feel that we can contribute back and put our efforts into something that can aid people and can provide a fun platform to share their thoughts, photos and media.
We don't even have a developer's pre-release. The reason it was announced in any fashion was because one of the core developers moved his site over and was the first person to actively use the code for his site. That's a MAJOR success, one that deserved to be celebrated. In a weird twist of fate, outing slightly earlier than anticipated was actually an incredible great thing. Why? Because people that were on the fringes, thinking that this was just all wishful thinking might actually hold some legs. As such this little buzz has gotten several people wanting to contribute, and here's one reason why:
Habari is a fresh start. We’re all in the unique position that we’ve been blogging for several years now. We’ve all had our share of experiences with open source and we’ve all seen several different packages in our time. We’re at the stage now that if we had a fresh start we’d do things slightly differently and hopefully better. And that’s what we’re aiming to do.
I guess that might be the greatest draw to the Habari project. We're pretty open for people who want to contribute to the project, in fact the way that this project has been set up, it's ideal for people wanting to contribute as it's got a completely different structure in it's development, in that it's a meritocracy. It's a great way to make sure that the software comes first and that there is no one person who veto's everything or has final say in everything.
So were do we go from here? Well one of the things that I shall be doing as I'm coordinating the designers on this team is to give a recap every Sunday of this week's activities on the design front. What we finished off and what we've got to look forward towards. I'll be including pics and so everyone is always welcome to chime in and add their two cents to the design either here or in the dev mailing list.
Well Chris broke the news about, Habari, a new open source blogging CMS platform. While he didn’t want feel it correct to mention in the post who was involved, I’m going to step forward and put my hand up as the designated pixel pushing monkey of this motley crew.
What I find amusing is that as this news was released by Chris, I read this post about how any new blogging software would not stand a chance because of WordPress. Man I love a fucking challenge. I mean reading that post you’d think we’d be fools to even consider making a WordPress alternative. I guess all I can say to that is: Colour us DAMN foolish.
Back in November Chris approached a few of us to see who would be up for helping design for the new project he was working on. His timing couldn't have been better to be honest with you. See I had a MASSIVE itch that just needed to be scratched. I had definitely not said everything that needed to be said about blogging administration panels, especially since the last one I was actively involved with didn't exactly go exactly the way it should have.
I felt pretty burnt the last time round to be honest, so much so that I really thought it was best for me to steer well clear of any open source involvement in the future. However like I said in that post the most important thing that I got out of the online experience was the collaboration with the guys. If it was anyone else asking me to do something apart from Michael, Joen and Chris I’d have probably declined there and then. I didn’t join the team because I didn’t have anything better to do (as it will become clear in the coming months), but alas because I really want to create something that I can be proud to have been involved with and that I will find a joy to use. Something that I can contribute towards and that others can contribute towards as well in an open fashion.
So when Chris came forward I was all too happy to say yes. Considering that I had actually contacted another developer (I’m not going to mention him by name but needless to say he was also having a similar itch which says a lot about how things stand in the current open source blogging world) about starting our own blogging CMS, it was interesting that others around me felt the need for an alternative as well.
The great thing about the Habari project is the fact that it's a clean slate. Imagine starting on the ground floor. There were no presidencies, no set stringent codebase that couldn't be altered, no existing userbase that might be confused and the list goes on. This is a decidedly different beast than Shuttle.
Those who don’t learn from the past end up repeating the mistakes again and again. So my approach to the graphical development of Habari is slightly different. Simply put, I’m going to be as transparent about the design process as you can imagine. I’ve seen several times in the past couple of months on the project, that through being open about the design I’ve been able to seriously move it forward in ways that I very well might not have considered. Ideas are what will make things move forward. At the same time it’s important that one person takes the bull by the horns and really goes to town on the design. Others should jump in with as many suggestions as possible, all the time because that’s how the innovation will continue and the project will not stagnate.
I will be going into a lot more detail in future posts regarding all the design decisions and what everything does and how it all fits together, so be patient, it'll all pay off in the long run I promise. As we've only recently kind of decided about colours (although knowing me I will probably tweak them, but I'm trying to be very good about this and sticking with this colour scheme), posting this will give people a feel of the quality of final product we're going for (and I'm not going to even talk about the code, the others are more than capable of that).
The following jpg is but a mockup, however Chris has implemented a fair chunk of this believe it or not (with probably like a 2 week old mock up), I’m telling you the man is a machine that will not be stopped. His dedication has forced me to make sure that I bring my very best to the table. It’s a bit of pressure that I’m actually relishing. Keeps me honest about things.