RE: Standard list of WCMS features

> It amazes me that still these days companies are building their own
> CMSs from scratch. That's risky business too, it may become costy if
> something goes wrong... 

And it isn't costly to pay vendors to fix their bugs...er...'unplanned
feature requests'? ;o)

> But
> still,isn't there a suitable CMS available with which you could start
> from? 

Had we the option to pursue open source options, perhaps. But even then,
except for the most basic of sites, I find most CMSes to have preconceived
ideas of what every particular user needs. If you have the staff, I say
build your own software. 

> What's wrong with a tool like Plone with which you are supposed to be
> able to do anything?

Well, what's wrong is the word 'supposed' ;o)

I honestly don't know a lot about Plone. The core of our research was around
.net technologies at the time, and, right now, we need to develop on .net
technologies (for better or worse...but that's debatable).

I have been (trying to) install some open source systems at home just to
play with. Plone is definitely on the list.

-Darrel