From: Sascha Ebach <se@...>
Date: 2005-01-16T20:02:33+09:00
Subject: Re: Ruby CMS

Francis Hwang schrieb:
> Right, but do you think that such a general CMS can satisfy the needs of 
> everybody? I'd say no, because people have vastly different needs for a 
> System that Manages their Content. ( This relates to that other thread 
> about too many Ruby web app frameworks: Part of the reason that there 
> are more than one is that the problem is too big and too varied to be 
> sensibly solved by any one framework anyway. )

No. No software can satisfy the needs of everybody. Not even Ruby ;) 
Take Rails for example. Rails does and behaves like David needs it to. 
My CMS will do and behave like I need it to. I hope that my needs will 
be similiar to those of others so they can use it, too. After all, it is 
going to be open source. And it should be easy to add your own 
functionality.

> When you say "blog that can later be a forum", whose blog is it? Just 
> one person? Or does each participant in the forum get their own blog? 
> How strong is the notion of identity--for example, do you have to create 
> an account to participate in the forum or is it as simple and transitory 
> as entering your email address in a blog comment form? How far do you 
> want your CRM to go? How tightly is the forum going to be integrated 
> with the blog, or with the online store?

As tight as you want it to be. But you will likely have to work a little 
bit on it.

> etc., etc. Software's important, but it's no substitute for strategy.

You have your own strategy. Maybe my CMS will allow you to implement it.

If you look at what people do with ezPublish and Drupal you will see 
that almost everybody customizes these packages to their needs. Almost 
nobody uses such software out of the box. Now imagine you could do that 
in Ruby...

Sascha