Habari , Wordpress and the others

[Dr.Hamza Mousa]

One ward , Habari is Magnificent , as wordpress guys used to say : Code is Poetry . i am ready a beautiful poerty .
However , i am interested in it's next move as more than a blogging system as i am interested as well in many usability features ( and they not hard to make ) in Habari .

such as :

1. Custom fields as a default ready feature  .( aS Wordpress , it'll exceed the creativity and use of the system for many uses - Portfolio , gallery , software directory , news reader , ....etc (i have many successful tryout with wordpress ) ) .
   
2. Widgets ready themes and templating system . 
3. simple feature as uploading or locating the plugin and themes as a Zip file , unziping and getting  them ready to work ( as Dotclear and Joomla ) .
4. Multi-sites Installation one admin panel ( Dotclear , and some others ) . 
5. Designing the needed sections  ( as Symphony http://21degrees.com.au/products/symphony/ i came cross this amazing one months ago , and the idea is awesome indeed try the demo . usually i do such thing with wordpress instead using the plugins i made ,i use custom fields and template tags to create the site i need just based on templating the idea . but that comes now with an ease with Symphony ) .

My major interest now is  about widgets , is there any plugin can do the trick ?!

--
Hamza E.e Mousa

www.neoxero.com
www.goomedic.com
www.medpeek.com

[Arthus Erea]

On Sep 12, 2008, at 2:20 PM, Dr.Hamza Mousa wrote:

One ward , Habari is Magnificent , as wordpress guys used to say : Code is Poetry . i am ready a beautiful poerty .
However , i am interested in it's next move as more than a blogging system as i am interested as well in many usability features ( and they not hard to make ) in Habari .

such as :

1. Custom fields as a default ready feature  .( aS Wordpress , it'll exceed the creativity and use of the system for many uses - Portfolio , gallery , software directory , news reader , ....etc (i have many successful tryout with wordpress ) ) .

Actually, Habari has support for something called "content types" – this basically means that you're not limited to just pages or entries. Already, there is an "event" content type, with the infrastructure to create more through plugins. The extensible content-types, the easy manipulation through FormUI, and the flexible template system make Habari an ideal system for developing all kinds of content. Instead of trying to coral this into custom fields, I think we'd rather see a variety of plugins developed for various types.

1. 
   
2. Widgets ready themes and templating system . 

We have a template system.

Instead of specifically building widgets, we're working on a flexible "hardpoint" system. This system would allow plugins to provide output to themes, which users could then control. Themes are a priority for 0.7 (I think) and I'm working on a branch to tackle this.

3. simple feature as uploading or locating the plugin and themes as a Zip file , unziping and getting  them ready to work ( as Dotclear and Joomla ) .

We're working on a plugin directory. On the client-side, see the HPM plugin – it seems to be moving in this direction.

4. Multi-sites Installation one admin panel ( Dotclear , and some others ) . 

I agree, but expect you'll see a lot of opposition to the idea. How our multi-site system is designed currently, the _only_ thing which is shared between sites is the source code. I think this merits careful and thoughtful discussion, especially from those who originally developed the system.

5. Designing the needed sections  ( as Symphony http://21degrees.com.au/products/symphony/ i came cross this amazing one months ago , and the idea is awesome indeed try the demo . usually i do such thing with wordpress instead using the plugins i made ,i use custom fields and template tags to create the site i need just based on templating the idea . but that comes now with an ease with Symphony ) .

I think that's trying to coral more functionality into Habari than is needed. Really, for the sort of things in there ("controller" anyone?) a full-blown framework would be best. First and foremost, Habari is a blog engine. That being said, we *do* have an amazing plugin architecture which allows for all kinds of things to be made (anything, really). However, I am very-much opposed to bloating Habari with framework functionality which should really be in plugins.

My major interest now is  about widgets , is there any plugin can do the trick ?!

Not currently.

[John Wrana]

I'm not an expert on the internals of Habari, but please keep it clean
and smart. Don't know if all the little features of other systems must
be combined in Habari.

I've used WordPress for 4 years and this blogging-system is meanwhile
so overbloated, so cluttered and the developers would like to target
every little wish and aspect and every two days there is a new
security-update... that was one of the reasons I moved to Habari and I
hope Habari will not just become a WP-clone, but an unique blogging-
system with its own style. An I like the direction Habari is
moving. :)

No need for widgets, imho.

> developed the system.> Designing the needed sections  ( as Symphonyhttp://21degrees.com.au/products/symphony/

[Dr.Hamza Mousa]

well said

i just tried the content type and it's really amazing , however i agree focusing on the idea of blogging system more than a framework , i also  believe the extensions ( plugins ) will be enough to increase it's capabilities is the best idea more than adding more features making it even complicated .

again well said
, i believe i'll stick with Habari , soon i figure out how to fix the wordpress updates ( it dose n't update all of myposts ) .

and thanks for the fast response

Regards

Hamza

[Dr.Hamza Mousa]

The Custom Fields plugin  is the content type i thought u mean ( which i tried ) !! even it's a plugin , but as i guess the Content Type will be embedded in the system and more like a feature .

[Arthus Erea]

Actually, I wasn't referring to the custom fields plugin so much as the content-type system in general.

Essentially, Habari makes it possible to develop brand new content types (just like entry and page) and then manipulate those content types however you want.

The Custom Fields plugin takes advantage of this, but in the end we'd like to see quite a few plugins which you can drop in to support various content types. Look at chyrp, for example.