Content management system
A content management system (CMS) is a computer software system for organizing and facilitating collaborative creation of documents and other content. A content management system is frequently a web application used for managing websites and web content, though in many cases, content management systems require special client software for editing and constructing articles. The market for content management systems remains fragmented, with many open-source and proprietary solutions available.
History
Content management systems were initially developed internally at organizations which were doing a lot of content publishing. In 1995, CNET spun out its internal development offerings into a separate company called Vignette. The company started offering the software as a web-based content management system, allowing sites to create templates of the presentation of their content on the web.
In 1998, Pencom Web Works, a consulting company, introduced the Metaphoria Data Transformation Server, allowing Java developers to write applications that would be tied with content and target the content output to different channels. The product failed but the concepts that were introduced by it made their way into most ancient content management systems.
In the early 2000s, many companies started offering weblog software which brought many of the concepts surrounding content management systems to the masses. Six Apart, with the release of their Movable Type quickly established itself as a leader in this field.
KKK
Types of content management systems
There are several types of content management systems:
- Web content management systems assist in automating various aspects of web publishing.
- Transactional content management systems (T-CMS) assist in managing e-commerce transactions.
- Integrated content management systems (I-CMS) assist in managing enterprise documents and content.
- Publications management systems (P-CMS) assist in managing the publications (manuals, books, help, guidelines, references) content life cycle.
- Learning management systems (L-CMS) assist in managing the web-based learning content life cycle. See also managed learning environment.
- Document imaging systems are also generally considered under the family of general content management.
- Enterprise content management systems (E-CMS) vary in their functionality. Some support both the web and publications content life cycle, while others support the web content life cycle and either transactional content or customer relationship management content. The definition of AIIM for ECM includes methods and tools for "capture, manage, store, preserve and deliver" content across an enterprise. "Manage" contains components like document management, collaboration, business process management, records management, email management, workflow and web content management. The ECM concept is not restricted to web based technologies but includes client/server and host based solutions.
See also
External links
This page or section may contain link spam masquerading as content. |
- Content Management Professionals Individual membership organization (Events, Case Studies, Best Practices, Resources)
- CMS Matrix Compare functionality of current CMS Systems.
- opensourcecms.com directory of opensource cms, hosting demos of php/mysql based free and open source software systems.
- AGIMO Australian Government Information Management Office (points 8-10 for CMS)
- StepTwo consultancy (Papers & Case Studies)]
- CMS Review
- OSCOM (CMS Selection Resources)
- CMS Info
- CMS Watch unbiased (but costly) comparisons of content management products
- List of Content Management Systems
- Reviews of Free CMS Software and Opensource Content Management Systems
- Open Source CMS List - another list of open source CMSs
- CMS Code Validation - a comprehensive list of CMSs with a valid code guide
- Software-Pointers - List of Content Management Tools
- CMSWire news, reviews, and product information related to content management systems
- The CMS Review
- CMS Wiki
- TopicWatch "Java Repository Specification" by David Nuescheler and Janus Boye.