Two things from my perspective with regard to what's been said so far: 1. In my understanding the standard plugin architecture as suggested by John gives us dead-simple Radiant plugin-ability to any forming or existing Rails app. This is probably the primary objective for my cases despite my whining about wanting to reuse my layouts, that and calling snippets / page parts in Rails views is a second priority for me.
2. I don't think we have to make the choice between "tight integration" of Radiant content into Rails views and simplicity of installation. They are different issues both with their own significant challenges, so it doesn't make sense to try and achieve both in the same release. So, I think addressing the plugin architecture issues first is good. From that basis we can then work- out integration issues (snippet helpers, layout reuse, etc.) I figure if we go that route we'll have more people using Radiant as a component of a larger Rails app sooner and therefore more input, effort and ideas being contributed to making the content integration stuff work as well and completely as possible. 3. I've used Comatose in a few projects and each of those cases I'd rather have used a plugged-in version of Radiant instead. It's a great project but I'd sure like to be leveraging my Radiant work and skills when I integrate. This also makes the transition with my clients from "we'll start with a simple content site" to "now let's build a custom app" less expense and painful. This is a common enough scenario for me. I'll put some more time into playing with Radiant installed as a plugin this week and see what trouble I find. Looks like you've gotten a good start on the right questions for me Sean and Matt. I'll report back on how far I get later this week. Loren On Jun 2, 2007, at 10:16 AM, Jed Hurt wrote: > Sean Cribbs wrote: >> I think Matt and Loren's cases are more about a tighter integration >> between Radiant and the host application, including reusing Radiant >> pages, layouts, and snippets in Rails. If you just want to add some >> content management to an existing Rails application, there's >> always the >> Comatose plugin, which has been around for a while and is probably >> better suited to that scenario. >> >> Sean > > I spent a little bit of time with Comatose this week. It's a cool > project, but a little bit too basic for my needs. I think we would > agree > that Radiant is—in many ways—an unparalleled CMS. > > -- > Posted via http://www.ruby-forum.com/. > _______________________________________________ > Radiant mailing list > Post: [email protected] > Search: http://radiantcms.org/mailing-list/search/ > Site: http://lists.radiantcms.org/mailman/listinfo/radiant _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
