Why Habari?

[BigFoot]

Hi all,

I am a Graphic Designer turned into Web Designer turned into Web
Developer.
One of the companies I develop for makes it excruciatingly difficult
to access the MySQL features of their websites and that's what has led
me to look into other alternatives, namely flat-file CMSs

I have done some research, at the following link you can view the
information I have collected on the topic in the form of a Blog post:
http://web-dev-cheat-sheets.blogspot.com/2009/08/flat-file-based-php-cmss.html

I have tried all of the Flat-file based PHP CMSs you see listed there
and I have to make a decision.
I have arrived to the following conclusions:
1- It should be SQLite-based so I can migrate painlessly later on if
needed
2- It should be actively developed

Could anybody provide me with additional arguments on why I should
choose Habari over the other candidates?


Thanks a bunch

[Andy C]

I'm not a developer just a humble user but I think Habari ACL system
is particularly well suited to a CMS with multiple authors as opposed
to a conventional (single-user) blog.

The other attractions aired by the clever developer types is the clean
code base, security, extensible architecture and a small but talented
Habari community willing to proffer assistance.

[ Don't ask me why no-one has had the courtesy to reply to this post
if Habari has such a brilliant community - maybe they are all
compiling lengthy dossiers packed with information :-) ]

For example, it's easy to use the ACL framework to quickly create a
simple registration plugin.

http://twofishcreative.com/michael/blog/2009/03/06/registration-plugin-for-habari

There's also another plugin for keeping revisions of articles which
would be useful for a CMS.

As for the cons, Habari is being actively developed (which you also
see as a 'Pro' :-) so the API isn't frozen and occasionally it can be
tricky to locate the correct version of plugins for the stable (0.6.2)
versus development (0.7).
--
Andy

On Sep 24, 6:55 am, BigFoot <rafael.minu...@gmail.com> wrote:
> Hi all,
>
> I am a Graphic Designer turned into Web Designer turned into Web
> Developer.
> One of the companies I develop for makes it excruciatingly difficult
> to access the MySQL features of their websites and that's what has led
> me to look into other alternatives, namely flat-file CMSs
>
> I have done some research, at the following link you can view the

> information I have collected on the topic in the form of a Blog post:http://web-dev-cheat-sheets.blogspot.com/2009/08/flat-file-based-php-...

[Michael C. Harris]

2009/9/25 Andy C <andy...@gmail.com>:

>
> [ Don't ask me why no-one has had the courtesy to reply to this post
> if Habari has such a brilliant community - maybe they are all
> compiling lengthy dossiers packed with information :-) ]

Fair go, Andy, it was on the todo list ;)

> On Sep 24, 6:55 am, BigFoot <rafael.minu...@gmail.com> wrote:
>>
>> Could anybody provide me with additional arguments on why I should
>> choose Habari over the other candidates?

While there are many reasons that could be given for choosing Habari,
it really depends on what your needs are. Your needs aren't really
clear from the post you linked (to me at least). I'll try to infer.

I haven't used it, but with the static cache plugin Habari can also
serve static files.

Habari's development philosophy is to have a small core, which means
you can use plugins to make it ... whatever you want.

It's got flexible template engines, so if you don't like what's there,
you can swap it out and use a different one.

And despite Andy's dig, we are a pretty welcoming and helpful
community :) If you've got specific questions or needs, we might be of
more help.

--
Michael C. Harris, School of CS&IT, RMIT University
http://twofishcreative.com/michael/blog
IRC: michaeltwofish #habari