[PhillyOnRails] Radiant CMS

[Flinn Mueller]

I like Comatose.  It's really good for expanding on because it is  
very simple and includes some niceties like sluggable urls (pretty  
urls), content caching, and a simple backend.  It also is easy to add  
into an existing project fairly well because it is a plugin and uses  
modular name space.  It plays nice on larger sites also.  I've done a  
lot of custom work with it, ranging from small sites with around 30  
or so page to a larger govt. site with ~400 pages, and I will be  
launching an ecommerce extended version with ~500 product pages real- 
soon-now.

Here's the project page: http://comatose.rubyforge.org/


On Jan 29, 2007, at 5:40 PM, Jonathan Van Schoick wrote:

> Hey guys,
>
> Is anyone using Radiant CMS? I've installed it and I'm playing  
> around with it, and it seems like a good choice for a project I'm  
> working on.
>
> Looking at it, though, I'm wondering about the best way to build  
> around it. For example, I have a basic contact form and some basic  
> shopping cart functionality set up. It's going to expand into a  
> full blown member section of a site. So should I try to keep the  
> Radiant section completely separate from the other app? My fear is  
> that if I entangle all my work into the Radiant rails app, it's  
> going to get messy and have conflicts.
>
> Any thoughts on working with Radiant or if you've run into a  
> similar type of situations? Any ideas are appreciated!
>
> -Jonathan
> _______________________________________________
> To unsubscribe or change your settings, visit:
> http://lists.phillyonrails.org/mailman/listinfo/talk