is Habari right for me?
craayzie
It's been pretty painful. This post does a decent job describing that
pain: http://www.phpvs.net/2009/12/08/an-exercise-in-wordpress-integration-or-why-wordpress-sucks/
I'm looking to build a site that, at it's core, is a cross between
WPMU and Ning: a multi-site install of WPMU + Buddypress. More
specifically, any user should be able to register for their own site
(e.g. user1.domain.com) and on this site they can create as many blogs
as they wish (e.g. user1.domain.com/blog1). I believe Habari supports
this type of multi-site install.
In it's full maturity, the site will have (in order of priority)
* premium services with pay-pal integration
* facebook/twitter activity feed integration
* iphone/mobile phone support (both publishing and viewing)
* social networking features
* ad-revenue sharing
It's possible to put together a prototype of the above in WPMU and I'm
getting close to shelling out $$$ to have someone develop it, but
longer term Wordpress just doesn't seem the way to go.
Is Habari the right platform for me to build on? Can you point me to
any "large" and/or heavily customized sites running Habari or _any_
sites running Habari for that matter? Anything else I should know
before taking the dive?
Thanks in advance for reading and replying and great work so far to
all the contributors, it looks like a great product!
Fima Leshinsky
rick c
development, Habari may not be the way to go to meet your goals for
the site. While Habari can serve multiple sites from the same code
base, each site has to be created and installed individually. While
the creation and installation can be scripted, Habari currently has no
internal mechanism to do the creation. Once they are created, there is
currently no way to administer each of the sites centrally. While a
plugin to do so could be written, and is something I'd like to see,
the capability isn't built in. Nor, at this time, are sites that live
in subdirectories (i.e., mysite.com/myblog ) possible. One can make a
site appear as if it lives at such a location, but to the best of my
knowledge, only once per site. This functionality is intended in the
future. Improving Habari's multisite capabilities is the intended
focus of Habari 0.8, but it isn't possible now.
http://wiki.habariproject.org/en/Multisite shows how multisite
installations are handled at the moment. If you look at
http://wiki.habariproject.org/en/Installation#Predefined_Configuration
, you'll see how a pre-filled out configuration file can be used to
automate installation.
Regarding some of the other features you listed, if plugins for the
functionality don't already exist ( take a look at http://habariproject.org/dist/plugins
), plugins for most of it should be possible.
Fima Leshinsky already pointed you to the list of Habari powered
sites. I don't know which of these are large or heavily customized. I
do know some individuals are using Habari in client work. Such work is
one source of the issues we find need improved with Habari. :)
Rick
On Mar 1, 1:18 am, craayzie <flesh...@gmail.com> wrote:
> For the last couple of months I've been learning/developing on WPMU.
> It's been pretty painful. This post does a decent job describing that
> pain:http://www.phpvs.net/2009/12/08/an-exercise-in-wordpress-integration-...
michael.twofish
contradict
anything.
Habari won't meet your needs out of the box right now, and will
require
changes to make it work the way you want. But those changes aren't
going to be
horrible hacks, they're going to be the implementation of what will
come
eventually anyway. And best yet, you'd get to have some say in how
those
things work in core.
On Mar 1, 11:32 pm, rick c <rickcock...@gmail.com> wrote:
> Welcome, craayzle. I hate to say it, but at this point in its
> development, Habari may not be the way to go to meet your goals for
> the site. While Habari can serve multiple sites from the same code
> base, each site has to be created and installed individually. While
> the creation and installation can be scripted, Habari currently has no
> internal mechanism to do the creation. Once they are created, there is
> currently no way to administer each of the sites centrally. While a
> plugin to do so could be written, and is something I'd like to see,
> the capability isn't built in. Nor, at this time, are sites that live
> in subdirectories (i.e., mysite.com/myblog ) possible. One can make a
> site appear as if it lives at such a location, but to the best of my
> knowledge, only once per site. This functionality is intended in the
> future. Improving Habari's multisite capabilities is the intended
> focus of Habari 0.8, but it isn't possible now.
>
> http://wiki.habariproject.org/en/Multisiteshows how multisite
> installations are handled at the moment. If you look athttp://wiki.habariproject.org/en/Installation#Predefined_Configuration
> , you'll see how a pre-filled out configuration file can be used to
> automate installation.
>
> Regarding some of the other features you listed, if plugins for the
> functionality don't already exist ( take a look athttp://habariproject.org/dist/plugins
Andy C
On Mar 3, 6:29 am, "michael.twofish" <michael.twof...@gmail.com>
wrote:
> >http://wiki.habariproject.org/en/Multisiteshowshow multisite
craayzie
want to do myself vs. paying someone else to do it. w/ Wordpress
there are a ton of development shops that I can turn to and w/ Habari
I'd have less options.
Now for the record WPMU isn't meeting my needs out of the box either
so with either platform there's going to be a significant investment
(time/effort/money) spent on development/customization.
If you were going to pay developers to build the kind of site I
described - do you think after all is said and done they could get
"more" developed using WPMU+Buddypress or Habari? I know that for
myself personally, I'd have a much easier time developing on Habari,
but I wonder how efficient the Wordpress development shops have gotten
at building features/customization after spending so much time with
the Wordpress code base?
In the end I want a product that "works" and if there's a group of
folks that's proficient in developing/customizing it then I'm happy to
have them do it. Or should I just stay away from developing on
Wordpress period?
Would love to hear your thoughts.
luke
I run a web dev company, and we've basically stopped doing any dev for
wp, because as efficient as we were, we're 10x faster on habari. A
clean code base works wonders. Having said that at the end of the day,
there are often other things that will slow you down more. can i
suggest first:
1) make sure you have a good solid knowledge of your requirements
first. Once you know these, then you can start making informed
decisions.
2) Once you know them, make sure you can communicate them well.
3) Once you know them, and can communicate them, then you can ask both
wp and habari devs, and get an idea of time and cost and feasibility.
Having just completed a site which was a very heavy customisation of
habari (think deviantart size, but industry specific), we look back
and can't imagine how we could have ever done it in wp. Having said
that, we started the project at 0.6.1, and even between there and
0.6.4 there have been lots of very useful patches that we have
required. Having a responsive dev team is key in this issue. Our
experience with wp was that if you found bugs, it was a bit like "well
done, wait 6 months", whereas with habari (Especially when they are
security related) there's a great philosophy of getting things done.
Good luck!
craayzie
started to work on. Your statement about stopping all develoment on
wp says a lot. Wow. Thank you again for sharing. Would love to hear
about others experiences as well.