On 30 November 2010 07:18, parndt <[email protected]> wrote: > > An easy call to make about whether or not you can use something like > > RefineryCMS is (a) are you handling a straightforward CMS site (e.g. a > > 'brochure site'), without a lot of customisation required for your > > content objects and (b) do you need to integrate with other APIs or > > systems and how well can the CMS handle it (does it insist on having a > > db table called 'Users', even though your shopping cart engine/plugin > > will want to mandate the same table with differently named columns, > > etc.). > > RefineryCMS can handle both straightforward sites and complex sites > because it's just built on Rails. What I mean by this is that if want > something custom then you can just add it in using an Engine or just > change the way the source code itself works. It is by no means a black > box system. We're even working on making it easy to just include the > RefineryCMS gem in your Gemfile, run our migrations and that's it > (work in progress). > > So, a) Doesn't matter for Refinery CMS and b) you can change any of > the table's names using set_table_name 'something_else' by modifying > the model using this approach: > > http://stackoverflow.com/questions/4018701/augmenting-a-model-from-an-external-gem/4019091#4019091 > or by copying the model file into app/models and doing it there. So > while we call it a "CMS" it is infact a pretty flexible system that > provides content management abilities to your Rails application which > may be a very complex system or one with specialised needs. > > Hope that helps. > > Refinery does look pretty nice, I think I'll give it a go :D
Thanks Daniel -- 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.
