It's kind of the other way around... Radiant *is* a Rails app, and, yes, it stores its pages in the db. But, you can write extensions, which are kind of like plugins, which is just like writing a rails app, meaning you have models, controllers, and views. And you can integrate these extensions into your Radiant instance, so that, to the end-user, it is all seemless. There are already a bunch of extensions that have been written that you can use, or you can write your own.
I would suggest going to the radiant wiki on github and checking out some of the documentation. Jamey On Thu, Jun 25, 2009 at 10:39 AM, Oran Topaz<[email protected]> wrote: > > Thanks for your kind answer, > > Just to understand in theory - When I use a regular CMS, I can't really > control the pages the way I like, or build my site framework nor my > database, as I am used to when building a regular app. > Is radiant CMS different? Could I create pages independently using my > favorite RoR IDE, and use radiant just to enjoy extensions and browser > customizations? Does it store pages on database like joomla which is a > major downgrade for me, or does it allow creating real html(.erb) > pages?? > Thank you, > Oran > -- > Posted via http://www.ruby-forum.com/. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
