> I'll second this advice. I may not know enough about your needs, but with a
> CMS, it doesn't seem importance what version of Rails or Ruby a CMS runs on,
> since a full-blown app is not what Radiant CMS is designed for.
That's exactly right.
>But I've been told that a Rails app can be written and included into a Radiant
>site as a plugin, although I haven't done that (yet).
That can be done successfully, I've worked with 3 or 4 apps like that.
It can also lead to code really hard to maintain.
Radiant is a really powerful CMS but in my experience as soon as you
start tweaking it adding features (as extensions) based around users
(signed up users, not the Radiant members) everything become
exponentially harder.
1) you are stuck with Rails 2
2) problems when you want to have static pages mixed up with dynamic
content, this requires radius_tags to pull in dymanic content which
are really powerful but not really like maintaining Rails views. Or
you can have your dynamic app pulling in CMS content doing something
like a Page.find.
3) you must source control the content where those radius_tags are
used, which means it will be harder to do diffs on templates
Basically you have to find out how much of the CMS you use, and how
much of 'new features' you will have to add.
If the latter is bigger, my suggestion is to go with a custom built
probably with help from Refinery CMS to get the CMS jump started.
HTH,
Enrico
