As an alternative approach, I like to break a CMS down into three parts: * describing the data model (which Rails is awesome at) * presenting the content in views (which Rails does pretty well with template language of your choice) * managing the content in the data model (eerie silence)
So, have you considered using one of the "magic admin backend" systems like Typus to handle the bit Rails doesn't do? To be clear, I don't particularly like those magic systems, but one of them might work for you or your clients! Justin On 01/07/2009, at 1:26 PM, Nicholas Faiz wrote: > > Hi, > > I'm trying to evaluate some CMS' out there for a couple of projects. > > I'm aware of Radiant, Mephisto, and BrowserCMS. Radiant relies upon > its > Radius templating heavily, and I want to use another templating > language. Mephisto is a bit too dusty these days - not even sure if > it's > up to Rails 2.3. BrowserCMS seems a bit restrictive on the browser > versions it relies upon. > > The other option is, of course, to build my own CMS, which I've done > before. Just wondering if anyone can recommend others I may not be > aware > of and which they have used themselves? > > Regards, > Nicholas Faiz > > > --- Justin French [email protected] http://justinfrench.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en -~----------~----~----~----~------~----~------~--~---
