RE: ASP dot Net CMS

I'm with a vendor of a .NET-based CMS.

In my experience, from the point of view of an end-customer trying to
implement a CMS-powered site, the choice of the technology platform (.NET
vs. LAMP vs. Java or other) has much more to do with path dependence in the
IT organization that it has to do with the relative merits of the platform
itself.  If an organization has an all-Microsoft infrastructure - all of the
existing servers and clients are MS, ergo all of the network management
scripts and tools and processes are MS-based, ergo all of the IT staff are
primarily skilled in and experienced with and certified in MS - it's simply
much more expensive and holds much more operational risk to choose a non-MS
solution.

The opposite is also true.  In our sales process one of the hardest sells is
to LAMP - infrastructure organizations.  No matter how excited we get them
about the capabilities a new Ektron-CMS-managed web site will provide, no
matter how much we get them salivating over the features or ease of use,
they cringe at the prospect of introducing a Windows server into their
infrastructure and finding IT staff to manage it.  We've fortunately found
it easy to assist with this process.

As far as the connotation of the term CMS, for Ektron and the other products
I've worked closely with, CMS does refer to a integrated, extensible,
content-centric or content-enabled web application infrastructure.

Tim Denby
Ektron, Inc.


-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Mat Griffin
Sent: Tuesday, February 22, 2005 10:56 AM
To: John; [email protected]
Subject: Re: [CMS] ASP dot Net CMS


Why are there so many blinkered people relying upon Microsoft products?
Trying looking a bit further than just MS.

I think there is a problem with the term CMS - many people developing sites
today with .NET are looking for integrated, extensible, content-centric or
content-enabled web application infrastructure, not typical templating
systems that simply generate static files which may end with aspx.