[thelist] content management systems?

[David Kutcher]

Martin,

While brining a highend solutions like Vignette into the picture, you're
immediately bringing the cost of the project to $100,000 US to $500,000
before integration or training even starts.

Yes, we're talking about a corporate solution, but almost 2/3's of the
companies that I've seen convinced into purchasing a license for Vignette
StoryServer, Blue Martini, Interwoven, or any of the others were also
convinced they needed a brand new server to run it, licenses for Oracle 8i+,
and more... when clearly this was an overkill and cost a cool half a mil.

Solutions like these do make sense in some situations, especially when
connecting to legacy systems or for massive publishing needs (I worked with
FoxNews to integrate Vignette).  But for the majority of instances out
there, I've found that "home rolled" solutions on a VA Linux server using
PHP and MySQL sufficed.

David
www.confluentforms.com


----- Original Message -----
From: <martin.p.burns at uk.pwcglobal.com>
To: <thelist at lists.evolt.org>
Sent: Thursday, February 21, 2002 10:47 AM
Subject: Re: [thelist] content management systems?
> >so it's better to
> >roll you own tool using something like zope which lets you "construct"
> >an app. using differents building blocks.
>  Nearly all grown-up CMSs do this - they're toolkits which you need to
> layer stuff on
> top of which relate to your specific needs. And if they're half-way
> sensible, then you
> can define your own building blocks either from primitives (right the way
> down to
> Java/Python/Perl/VB/whatever code) or from their provided composites.

> Most packaged CMSs and linked packaged products (eg Vignette, together
with
> Verity, as a front end to an ERP like SAP to pick a high-end product set,
> and
> similar bundles could be put together at a lower end) now can do*enough*
of
> the things you'll need for nearly any purpose (and almost *all* of the
> supporting
> functionality like searching, user/security management, workflow etc) that
> unless
> you want to compete as a vendor, you just wouldn't ever write one from
> scratch
> for a client.
> Other than
> the personal sense of achievement, why would you want to do that for
> yourself? And why would a paying client want you to develop it from
> scratch?
>
> Cheers
> Martin