[thelist] Help with Social Network/Community Functionality

[Barney Carroll]

Hi Randal,

For me this would have to be one of two things:

a) Drupal [http://drupal.org]
I'm very cynical of Drupal as CMS for most applications but I think it could
be very useful here: custom content types (recipes), user histories and user
browsing are some of the things that are very quick and easy to get out of
Drupal. It's also very easy to customise lists of "recently commented on" or
"hot recipes" or whatever. Drupal is built with community contribution in
mind and stands at a halfway house between ye olde forum and the modern
understanding of 'social networking site'.

b) Elgg [http://elgg.org]
Alternatively if you want all the trappings of web 2.0 and more Facebookish
features like elaborate user profiles; open, private or invite-only groups,
events and all sorts of other generic content types and interactions we've
come to expect of social networking, and advanced custom content types and
quick hacking aren't important to you, I'd go with Elgg.

I would add that Drupal has a huge community of users contributing modules
and plugins, and are very responsive to cries for help and advice on
anything Drupal-related; and also that while Elgg is incredibly quick to
style and present as your own, it's much harder to do any serious tweaking
and customisation.


Regards,
Barney Carroll

barney.carroll at gmail.com
07594 506 381


2009/6/29 Randal Rust <randalrust at gmail.com>

> On Mon, Jun 29, 2009 at 4:39 PM, Paul Bennett<Paul.Bennett at mch.govt.nz>
> wrote:
>
> > Not sure if you're looking for suggestions or a tool / framework to do
> > the heavy lifting for you.
>
> Suggestions:)
>
> We have our own custom-built framework where we can certainly mix and
> match content as the client wants. The issue is that what they are
> asking for creates a very confusing, unusable situation for both
> members and administrators. We are developing this portal for another
> company as a subcontractor.
>
> The problem is that our client thinks it is a good idea to be able to
> approve a story, yet reject the photo -- even though they are
> submitted at the same time, as part of one unit -- if that makes
> sense. It's like saying the car is OK, but we'd like different tires
> -- after the order has been placed and the car has been delivered. It
> creates, in my mind, unnecessary complexity.
>
> FWIW, I have spent some time going over Drupal. In fact, we have spent
> a good bit of time studying the code.
>
> --
> Randal Rust
> R.Squared Communications
> www.r2communications.com
> 614-370-0036
> --
>
> * * Please support the community that supports you.  * *
> http://evolt.org/help_support_evolt/
>
> For unsubscribe and other options, including the Tip Harvester
> and archives of thelist go to: http://lists.evolt.org
> Workers of the Web, evolt !
>