Hassan Schroeder wrote:
Paul Noone wrote:
Semantics, semantics. Contribute is used for client-side WYSIWYG content
publishing across an enterprise. It may not fit with the current
browser-based varietals currently in abundance but it is still a system used
to manage content, albeit one which is dependent on Dreamwever templates.
Respectfully, I think it's really stretching the definition beyond
the bounds to characterize Contribute as a "CMS". I can edit and
publish content using jEdit or emacs -- what's the diff?
Contribute creates no change logs or audit trail, does no version
tracking, has no innate concept of a site's architecture, and so on...
Interwoven's TeamSite is a CMS. Documentum is a CMS. ATG Dynamo is
a CMS. There's a *lot* of software I see called a "CMS" on this and
other lists that make me have to bite my tongue big time -- but
Contribute? It's an editor. IMHO :-)
And yes, YMMV (as you guessed)
Seeing I started this thread, and Paul was just trying to help me out,
I'll take the blame for the confusion. Yes, I know Contribute is not a
CMS, and many of the applications that are discussed on this list may
not fit the true definition of a CMS, but for developers who try to work
and maintain web standards, we are often forced to cobble together
anything possible so that users can manage content on their sites whilst
trying to preserve the integrity of the code that is used to build the
interface.
In this particular instance, a text box area for adding content, as in
TXP, etc, does not meet the clients needs, that's why I asked some
questions about MMCont. Also, it is not completely clear as to whether
or not that MMCont3 is evolving into a CMS with it's server component
now. Thankfully Paul and some of the others saved me a lot of time and
pain by clarifying how it works. Thanks guys (and dolls).
------------------
Geoff Deering
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************
