Posts filed under "habari"
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.
The Installer
The installer now is broken down in several sections, and Owen came up with the idea whereby this area might be further customised by developers to make it easier to do things and incorporate elements so that it’s easier to administer new installations (or something like that, best talk to him about that). The design follows through the idea to keep things simple and as modular as possible.
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.
Create Page
The main page has gone back a step. Originally all the Habari mockups were done in blacks and shades of grey however as the design ‘progressed’ colour started being added. We’ve taken a step back to confirm how everything fits together before we move later on down the line for the full branding of the application.
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.
Logo
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:
Installer
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.
Administration Panel
Very minor tweaks going on here, except of course the colours. The pink is displayed for when you hover over the log out button.
Publish
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.
On Community
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.
So you’re aiming to kill WordPress?
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.
Habari Contribution Model
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.
History Lesson
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.
Shuttle vs Habari
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.
The Design
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.
Final Thoughts
If you’ve got ideas you think the ultimate BLOGGING CMS should have drop a comment, I’d love to hear what ideas everyone has and what’s important to them as a user. What is it about your current blogging software that you wish could be simplified/improved, I’m all ears.