I wish people would stop calling Drupal a Content Management System,
its a canned community (or “Community Management System”) that happens
to give you the ability to edit and categorize some content. It is
very weak in the workflow department, nor does it support content
outside of the Web paradigm very well (to this day, there isn’t even a
decent File/Document Management component).
So then have a decent look of typo3, and you are proofed wrong.
In fact, 90% of the Web-based CMSs are Community Management Systems –
and they’re not much better. Each piece of the puzzle has rough edges
or is tightly-coupled to a set usage: it really is a shame that so
much of the community development process is wasted on very
un-DRY-like activities, like writing an Amazon booklist widget or a
“shoutbox”… 27 times, in 27 different PHP CMSs.
Yeah, that is what most people are missing in typo3, the community
And the same un-DRY activities pop up here in the RailsCommunity,
otherwise you canT
explain the various activities and starting CMS packages all over the
web based on RoR, out of
my head I could call at least 3 or 4 yet.
None of them will have only the chance to compete with something as
typo3 for the next couple of years.
Anything prooving me wrong is very welcome, cause I would also prefer
rails over php, but one has to be pragmatic, not ?
How many authentication/login systems do we have, how much
globalisationProjects are on its way…etc pp
This repeated stuff isnt the fault of php nor of RoR, its based on the
fact, that pl think they are faster, better if they reinvent the
wheel cause their needs are going beyond of what they get right now…
engine, dynamic menus, and basic CRUD content entry – is pretty much
RoR/OO train of thought puts interop and loose coupling at a premium
meaning that things tend to play nicely together.
Unless you’re building a canned community, I’d choose RoR.
Unless you dont have to deal with various editors once the site is
running, or even various levels
of editors, decent rightsmanagement for each step in the publishing
process unless you dont need
clever multilanguagesitesetup and contentmanagement, unless you dont
need…go with Rails, and make
sure to post us an URL for the project once you have finished it
So, just to avoid any confusion: I dont argue against RoR at any point,
I dont argue for php either, I would
prefer RoR over any phpsolution, BUT “he” was looking for a CMS TODAY,
"he " wasnt asking what happens, if
one farday he would need to use a CMS but also extend it probably…this
is all that vague…I think this whole discussioon
was quite useless as the starter left us assuming , assuming,
assuming…instaed of sketching out his needs in detail and
asking based on that, but I wonder if he has sketched his needs for
Anyway, I am out of this discussion at this point…
There must be a difference between pragmatic and fanatic at some point,
and for sure one could (re)build phpbb or oscommerce in RoR,
but then, who will, how long will it take…and better, where is this