[rails-oceania] Re: evaluating CMS'

BrowserCMS does sound promising. I've never really found a CMS which could be used for every project. If anyone has ever used Plone they'll know the cringe factor which can eventuate from trying to achieve this. I'll probably end up playing with BrowserCMS at some stage. Cheers, N. On Jul 3, 1

[rails-oceania] Re: evaluating CMS'

I have been getting into Radiant, and its a pretty good option if you're a Ruby developer and your clients just need a simple admin interface to edit a brochure site, but with the massive customisation ability that Ruby tends to provide. Its also highly efficient as content is cached and served st

[rails-oceania] Re: evaluating CMS'

I've rolled my own in the past. If you're going for a traditional backend/front end approach you might look into active scaffold to jump start your admin interface. On 01/07/2009, at 8:21 PM, Nicholas Faiz wrote: > > There's also > > * the hierarchical structure of content - for example, fol

[rails-oceania] Re: evaluating CMS'

There's also * the hierarchical structure of content - for example, folders holding pages, or sub-pages of pages. Something acts_as_tree or a nested set will give you. * basic security - some notion of which user can manipulate which content * versioning - not always a requirement, but usually. N

[rails-oceania] Re: evaluating CMS'

As an alternative approach, I like to break a CMS down into three parts: * describing the data model (which Rails is awesome at) * presenting the content in views (which Rails does pretty well with template language of your choice) * managing the content in the data model (eerie silence) So, h

[rails-oceania] Re: evaluating CMS'

I thought of that - it's ideal really, except that I need versioning. Otherwise, spot on! ;) On Jul 1, 4:06 pm, Lawrence Pit wrote: > Given the usual absence of any requirements I suggest Twitter. Great > CMS. Even Britney and the PM appear to be able to use it. > > > I am intrigued by Tim Luca

[rails-oceania] Re: evaluating CMS'

"Given the .. absence of any requirements" - I love that :) On Wed, Jul 1, 2009 at 4:06 PM, Lawrence Pit wrote: > > Given the usual absence of any requirements I suggest Twitter. Great CMS. > Even Britney and the PM appear to be able to use it. > > I am intrigued by Tim Lucas's CMS-by-Github app

[rails-oceania] Re: evaluating CMS'

Given the usual absence of any requirements I suggest Twitter. Great CMS. Even Britney and the PM appear to be able to use it. > I am intrigued by Tim Lucas's CMS-by-Github approach. It was sweet. > > On Wed, Jul 1, 2009 at 1:26 PM, Nicholas Faiz > wrote: > > >

[rails-oceania] Re: evaluating CMS'

Julio - it's for a client, so it has to have some polish in the admin UI. Others, on Mephisto - yes, I run Mephisto for my website (http:// treefallinginthewoods.com) and helped contribute the Plugin API to it ages ago. It isn't seeing a lot of activity that I've noticed - and it does seem to spe

[rails-oceania] Re: evaluating CMS'

Even so, it's flexible enough to be used as one - I use it for all content at my blog site, with great success. It has obvious limitations, but for a blog site with tidbits of content that are not blog articles, it works very well. -- Kirk Bushell http://www.kirkbushell.com Follow me: http://twi

[rails-oceania] Re: evaluating CMS'

On 01/07/2009, at 1:26 PM, Nicholas Faiz wrote: > Mephisto is a bit too dusty these days - not even sure if it's up to > Rails 2.3. Mephisto is still being actively developed (0.8.2 was released this year and works with the 2-2-stable branch / 2.2.2 tag of Rails). That being said, it's more

[rails-oceania] Re: evaluating CMS'

Righto - thanks. Right now I'm looking at how hard it is to hook other templating languages into Radiant, instead of Radius. I'll probably go with Radiant if that's feasible. On Jul 1, 2:09 pm, Tim Lucas wrote: > On 01/07/2009, at 1:36 PM, Dr Nic Williams wrote: > > > I am intrigued by Tim Lucas

[rails-oceania] Re: evaluating CMS'

Nicholas, is that for your own use? In which case I'd wager a "hacky" way to post is fine (as opposed to a web interface + rich editing). For a recent project I created a post via capistrano thing that worked really well. I'd create a directory with a text file in it (first line becomes the post

[rails-oceania] Re: evaluating CMS'

On 01/07/2009, at 1:36 PM, Dr Nic Williams wrote: > I am intrigued by Tim Lucas's CMS-by-Github approach. It was sweet. ...which was: give them access to github and let them edit haml files directly via the github web interface. Git pull redeploy the site (or just the markdown files) on post

[rails-oceania] Re: evaluating CMS'

I am intrigued by Tim Lucas's CMS-by-Github approach. It was sweet. On Wed, Jul 1, 2009 at 1:26 PM, Nicholas Faiz wrote: > > Hi, > > I'm trying to evaluate some CMS' out there for a couple of projects. > > I'm aware of Radiant, Mephisto, and BrowserCMS. Radiant relies upon its > Radius templating