Radiant is built using Ruby on Rails. This means it's easy for developers to extend Radiant because it's built on a widely accepted (and understood) Web application development platform.
just to go ahead and state my position, i agree with jonathan. he laid
it out just as i would. in my capacity as a web development consultant
for non-profits, i would never set up a drupal site and walk away
(unless it was a non-profit of drupal developers). joomla is by far
the choice if the end user(s) are not into hacking code.
if you don't want to do much, wordpress is awesome. wordpress is the
first thing that has actually made me think PHP was worthwhile.
My dislike of PHP is why the Sopo site is running on a CMS that i'm
developing in Perl. I'm almost ready to open up the code for anyone to
use. if you're good with AJAX feel free to volunteer to help out with
me finishing up.
On 10/11/07, Simon Z < youractionsdefineyou@gmail.com> wrote:
> I have to recommend drupal too.
>
> PROS: Aside from ease of use, it is free and all its modules are free
> and it is widely used in the non-profit / radical community which makes
> cross-networking very easy.
>
> CONS: you need to know some php or css to create a site that looks
> really different from the basic formats / themes.
>
> Simon
>
>
> Andrew Bushaw wrote:
> > We have been using pbwiki.com (a free wiki, one login) for our
> > organizing but are starting to feel the need for a tiered access
> > control as well as for an actual website to send the public to. We
> > have been contemplating getting a content management system such as
> > "drupal" to serve both functions. I think the SLBC uses a similar CMS
> > for their website and maybe others do to. How well does it work? Do
> > regular folks have a difficult time using it? our ideal: public web
> > page w/ donation links, a login page with a volunteer only section,
> > then a section for core members only where we would keep fundraising
> > info. Would like it to be easy to edit, with a wiki-like interface,
> > preferably wysiwyg editors. Thanks, Andrew
> >
> > _______________________________________________
> > Thethinktank mailing list
> > Thethinktank@lists.bikecollectives.org
> > http://lists.bikecollectives.org/listinfo.cgi/thethinktank-bikecollectives.org
> >
> >
>
> _______________________________________________
> Thethinktank mailing list
> Thethinktank@lists.bikecollectives.org
> http://lists.bikecollectives.org/listinfo.cgi/thethinktank-bikecollectives.org
>
_______________________________________________
Thethinktank mailing list
Thethinktank@lists.bikecollectives.org
http://lists.bikecollectives.org/listinfo.cgi/thethinktank-bikecollectives.org