Youssef,
This is the perennial question. I should make a wiki page for it!
Although there are a million variations on them, the three main
strategies are thus -
1) Build customizations/other apps as Radiant extensions (most popular)
2) Keep Radiant and your other app in parallel, as separate apps (works
for shopify.com and dozens of others)
3) Start with Radiant as the base (not in vendor) and add your
customizations on top (Ba did this IIRC)
If you want a more detailed discussion of the benefits and caveats of
each, let me know. "Mountable apps" are in the near future for Rails,
so you may see Radiant do that eventually.
Sean
Youssef Chaker wrote:
Hey guys,
I am new to Radiant, in fact I haven't done anything with it yet. But i've
been struggling with Drupal and ExpressionEngine and want to move toward
something that uses ruby and would really like to be able to pitch radiant
to my boss or my clients. One of the main questions i have about adopting
Radiant, is whether it is possible to integerate Radiant with an aleady
existinig rails app. and if it is, how easy is that process and can anyone
point me to a tutorial?
In many cases of the pojects i've been on, there was always the need for
custom code but also some form of content management system on the side for
static content that the client can easily edit and such. So if you guys have
any pointers on the subject, i would really appreciate it.
thanks.
_______________________________________________
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
