Sorry it took so long to respond.  Was trying to find a way to reply via
google groups :P

We're definitely looking at this from the perspective that we'll need to
develop a lot of features ourselves.  The goal is to see if we can start
with a framework that has some of the things we need out of the box so we're
not re-inventing the wheel.

I need to think through your comments a bit more and explore some of the
other options out there (pure blogging frameworks like typo and some of the
newer ones out there) before I follow up w/ more questions.  Thank you again
for the detailed responses.

If you know of any good radiant-based blogging sites/communities out there
I'd love to take a look at them.

Fima

Date: Tue, 23 Mar 2010 10:55:56 -0700
From: banane <ban...@gmail.com>
Subject: Re: [Radiant] is Radiant the right platform for our project?
To: radiant@radiantcms.org

It really sounds like more of a drupal/joomla option (portals!) than a
Ruby on Rails/Radiant one. But the benefits of choosing Radiant:
- it can be a portal, including paypal and blogging
- the support network is vast (many rubyists)
- there is a distinction between the administrators/writers/viewers,
and it's very clear.

I'm actually shocked that you considered WPMU as that would get ugly
fast ;) There are enterprise-level private software options for
large-scale deployments.

one thing to consider with Christian's remarks:
- caching removes the necessity of hierarchical lag times
- I doubt Radius tags would play in this much, except perhaps for the
portal-esque aspects of the site.

Regarding your checklist:
- private messaging. Currently haven't seen an extension that does
this, though you could write your own of course.
- member profiles, same as above
- photo publishing experience. Not sure what this means. Adding and
displaying your own photos? You may have to extend an existing
extension.
- mobile support- also not sure. You mean the site reduces to a mobile
version? Also haven't heard of one (though there could be one)
- paypal integration- I've done this with WP and it's pretty much in
PayPal's court. The elements in the site are minimal, and analytics-
for google, at least, there are 3 or so extensions that do this.  Not
sure what "premium features" are.
- private/public sites/blogs  - well, radiant is built for the public
site. The private? There are user extensions, and administrative side,
and setting up userAuth is easy, so I could imagine this could be done
easily. I am not aware of an extension for it specifically.

With all that in mind, for a kind of spec that you're defining,
usually that is homegrown.

Anna

On Tue, Mar 23, 2010 at 1:58 AM, Christian Aust
<christian.a...@software-consultant.net> wrote:
> Hi Fima,
>
> what I love most about radiant is actually its extensibility plus the
clean programming model that comes with Ruby on rails apps in general.
Extending existing classes, adding your own models? Adding functionality to
the lifecycle of entities? Custom rake tasks? It's all just some lines of
code, clean and maintainable. Add specs and scripted deployment using
Capistrano, and you're ready to go.
>
> Having said that, radiant itself seems to be targeted at projects
involving small teams of dozens of users (with less administrative overhead)
and rather low numbers of pages. Having thousands of users with hundreds of
roles creating 10.000 pages isn't something that the standard radiant code
base of radiant will handle too well. (This is my very personal opinion, I'd
like to hear otherwise)
>
> [What I'm thinking about is the instantiation of Page objects, for
example. Traversing very large trees of pages could lead to an increasing
number of database queries quickly.]
>
> Plus, one of the strongest parts of radiant is the concept of radius tags,
AFAIAC. Could you actually make use of them in such a scenario? Would users
create blogs using radius tags? Or would you use them during development
only? If so, you'd sooner or later recognize that implementations of radius
tags are somewhat separated from the standard rails concept of controllers
and helpers, let alone request and response data. This is perfectly fine for
what they've been designed to do (give access to functionality of your data
model within the view), but needs tweaks and workarounds when developers
need some more low-level capabilities.
>
> Reading your list of requirements, I assume that most if not all has at
least some opensource component to start from. Regarding radiant, it feels
like you'd disable or ignore most of it's standard features and
capabilities, basically building your own app around it. Maybe you're better
off starting with a general-purpose rails template and adding stuff from the
radiant code base that fits your requirements well.
>
> Regards,
>
> Christian
>
> Am 23.03.2010 um 07:21 schrieb Fima Leshinsky:
>
>> Additionally, (very high-level) requirements are:
>>
>> * premium features + paypal integration (think premium themes, analytics,
>> etc.)
>> * social technologies (member profiles, messaging, etc.)
>> * strong photo publishing experience
>> * mobile support
>> * private/public sites and blogs
>
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
List Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant: http://radiantcms.org
Extensions: http://ext.radiantcms.org

Reply via email to