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: [email protected] 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
