WEB CONTENT MANAGEMENT SYSTEM
•Content management system software is inplemented in a web application for creating and managing HTML content. •It is used to manage and control large number of dynamic collection of datas. •It is useful and facilitates content creation,content control,editing and web maintenance function. •Most systems use a database to store content, metadata, or artifacts that might be needed by the system. Content is frequently, but not universally, stored as XML, to facilitate, reuse, and enable flexible presentation options. •A presentation layer displays the content to Website visitors based on a set of templates. The templates are sometimes XSLT files •Unlike Website builders, a WCMS allows nontechnical users to make changes to a website with little training. A WCMS typically requires an experienced coder to set up and add features, but is primarily a Website maintenance tool for nontechnical administrators •Allow for a large number of people to contribute to and share stored data. •Control access to data, based on user roles. User roles define what information each user can view or edit. •Aid in easy storage and retrieval of data. •Reduce repetitive duplicate input. •Improve the ease of report writing. •Improve communication between users.
Capabilities of a Content Management System:
A WEB Content Management System typically has the capability are: •Automated template •Easily editable content •Scalable features sets •Web standard upgrades •Work flow management •Delegation •Document management •Content virtualization •Content syndication •Multilingual
Types of WCMS:
There are three major types of WCMS are: •Offline Processing •Online Processing:
Most open source WCMSs have the capability to support addons, which provide extended capabilities including forums, blog, wiki, webstores, photogalleries, contact management, etc. These are often called modules, nodes, widgets, addons or extensions. Addons may be based on an opensource or paid licence model. •Hybrid System: Some systems combine the offline and online approaches. Some systems write out executable code (e.g. JSP, ASP, PHP, ColdFusion, or Perl pages) rather than just static HTML, so that the CMS itself does not need to be deployed on every Web server. Other hybrids operate in either an online or offline mode