Mario T. Lanza wrote: > I totally get your positions and I like that Radiant is geared toward > those camps. It's just that those are the people who are seemingly > wanting to combine it with custom Rails pages and are asking about the > best practices concerning it. One there is a model way for > accomplishing this, the sky will be the limit with using Radiant for > developing custom, content-centric website. At that point, everything > else will be bells and whistles. :)
It's almost a coincidence that Radiant is programmed in Rails. Yes Radiant is a Rails application, and yes we are going to try and make it somewhat easier to integrate a small part of a Rails app with Radiant, but Radiant is first and foremost a static information oriented content management system made for designers. It is not a custom portal system or a "content management framework for Rails". The Extension system is there to make it easy to extend the admin interface. Replacing your Rails app with Radiant and a ton of custom extensions is probably a bad idea (unless your Rails app is primarily an information oriented CMS). If you have a Rails app that you want to add a few CMS features to, the Comatose Rails plugin is probably a better choice. Keep in mind that Radiant is trying to be a better Movable Type or Textpattern--not a Drubal or Zope for Rails. There is a ton of room for a portal framework in the Rails CMS space. Radiant will never be that type of CMS. -- John Long http://wiseheartdesign.com _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
