Youssef Chaker wrote:
Thanks Sean and Jim for your answers. It seems that the second method suggested is the only one applicable to my scenario where I already have a massive app that exists and the static content would be a very small portion of the site and that's why I was considering Radiant to manage that aspect of it. And working on managing my app and Radiant in parallel seems to not be worth the effort in that particular case. But thank your for your suggestions, i will probably use Radiant for another app where i'm starting from scratch and that will make it easy to build my custom stuff on top of Radiant.
If all you need is a bunch of semi-static content that is available and visible to all who go to the website (such as Help documentation, etc), why not run Radiant on a different sub-domain? It could do most of what you may need. So, you could have docs.example.com serving all the static stuff but managed within Radiant.
However, your memory footprint will go up since Radiant will need its own installation/ running Mongrels.
Finally, there was an extension that produced static pages from a Radiant site; if your content is really static, this could be a great way to get the best of Radiant and update the site's static stuff in Radiant every time something changed - and then produce the static pages and upload.
Cheers, Mohit. 3/17/2009 | 10:31 PM. _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
