[Rails] Re: CMS and REST - best practices

2009-05-13 Thread John Small
wejrow...@gmail.com wrote: No, I want to build it myself.. I look at it though. So what is the best practice? Should I build a separate section with its own controllers to edit them? or make a separate private view within the component controller? I started looking at Adva (see

[Rails] Re: CMS and REST - best practices

2009-05-13 Thread Francesc Esplugas
On Wed, May 13, 2009 at 9:39 AM, John Small rails-mailing-l...@andreas-s.net wrote: The other thing I don't like about it is the assumption that a CMS is used solely for publishing articles. I guess if you spend your life blogging then that's a sensible assumption, but most websites aren't

[Rails] Re: CMS and REST - best practices

2009-05-11 Thread Mohit Sindhwani
wejrow...@gmail.com wrote: OK I need a bit of direction for this. I want to build an app where I have a CMS side that edits everything (which is all private), then a public side which just views is all. My dilemma is how to set this up. What is the best practice for this? I have a couple

[Rails] Re: CMS and REST - best practices

2009-05-11 Thread Mauricio Dulce
hello, i need add the comments to radiant please i neet a tutorial thanks El 11/05/2009, a las 20:16, Mohit Sindhwani escribió: wejrow...@gmail.com wrote: OK I need a bit of direction for this. I want to build an app where I have a CMS side that edits everything (which is all private), then

[Rails] Re: CMS and REST - best practices

2009-05-11 Thread Mohit Sindhwani
Mauricio Dulce wrote: hello, i need add the comments to radiant please i neet a tutorial It would be good to ask on the Radiant CMS mailing list, but see: * http://github.com/saturnflyer/radiant-comments/tree/master * http://wiki.github.com/radiant/radiant/using-radiant-as-a-blog Cheers,

[Rails] Re: CMS and REST - best practices

2009-05-11 Thread wejrow...@gmail.com
No, I want to build it myself.. I look at it though. So what is the best practice? Should I build a separate section with its own controllers to edit them? or make a separate private view within the component controller? --~--~-~--~~~---~--~~ You received this