Title: Web Content Management System Year: 2011-2012 Group id: 6 Project Description:

Web Content management system (CMS) supports the creation, management, distribution, publishing of web content. It covers the complete lifecycle of the pages on a site, from providing simple tools to create the content, through to publishing, and finally to archiving. It also provides the ability to manage the structure of the site, the appearance of the published pages, and the navigation provided to the users. A CMS used to manage web content is called a web management system (WMS). Its functionality can be broken down into content creation, content management, publishing, and presentation. At the front of a content management system is an easy-to-use authoring environment, designed to work like Word. This provides a non-technical way of creating new pages or updating content, without having to know any HTML. It also allows managing the structure of the site that is, where the pages go, and how they are linked together. Once a page has been created, it is saved into a central repository in the CMS. The CMS keeps track of all the versions of a page, and who changed what and when, ensuring that each user can only change the section of the site they are responsible for and integrate it with existing information sources and IT systems. At each step, the CMS manages the status of the page, notifying the people involved, and escalating jobs where required. Once the final content is in the repository, it can then be published out to either the website or intranet. Content management systems boast powerful publishing engines, which allow the appearance and page layout of the site to be applied automatically during publishing. CMS lets the graphic designers and web developers specify the appearance that is applied by the system. These publishing capabilities ensure that the pages are consistent across the entire site, and enable a very high standard of appearance. This also allows the authors to concentrate on writing the content, by leaving the look of the site entirely to the CMS. The CMS fully automates the publishing of your site.

The content management system can also provide a number of features to enhance the quality and effectiveness of the site itself. The CMS can be used to make your site dynamic and interactive, thereby enhancing the site's impact.

Scope:
The idea is to design a software program that will take care of the new web pages to be added according to new products being added automatically. All the user/administrator has to do is add the new product/item/service details to database and the program will automatically add the item to the companys website by adding new required pages as well as refreshing the links to these newly added pages from other pages. It also maintains regular backups for the company website for fast restoration in case of server failure.

Objective:
Content management systems are relatively new in the market, and while many are still not familiar with them, they have the potential to dramatically simplify the maintenance of both websites and intranets.

Relevant Theory:
Web Content Management System
A Web content management system (WCMS or Web CMS) is content management system (CMS) software, usually implemented as a Web application, for creating and managing HTML content. It is used to manage and control a large, dynamic collection of Web material (HTML documents and their associated images). A WCMS facilitates content creation, content control, editing, and many essential Web maintenance functions. Usually the software provides authoring (and other) tools designed to allow users with little or no knowledge of programming languages or markup languages to create and manage content with relative ease of use.

Most systems use a database to store content, metadata, and/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 regular Web-site visitors based on a set of templates. The templates are sometimes XSLT files. Administration is typically done through browser-based interfaces, but some systems require the use of a fat client. Unlike Web-site builders like Microsoft FrontPage or Adobe Dreamweaver, a WCMS allows nontechnical users to make changes to an existing website with little or no training. A WCMS typically requires an experienced coder to set up and add features, but is primarily a Web-site maintenance tool for non-technical administrators

What are the key features?

A WCMS is a software system used to manage and control a large, dynamic collection of Web material (HTML documents and their associated images). A CMS facilitates document control, auditing, editing, and timeline management. A WCMS provides the following key features: o Automated templates: Create standard output templates (usually HTML and XML) that can be automatically applied to new and existing content, allowing the appearance of all of that content to be changed from one central place. o Easily editable content: Once content is separated from the visual presentation of a site, it usually becomes much easier and quicker to edit and manipulate. Most WCMS software includes WYSIWYG editing tools allowing non-technical individuals to create and edit content. o o o Scalable feature sets: Most WCMS software includes plug-ins or modules that can be easily installed to extend an existing site's functionality. Web standards upgrades: Active WCMS software usually receives regular updates that include new feature sets and keep the system up to current web standards. Workflow management: Workflow is the process of creating cycles of sequential and parallel tasks that must be accomplished in the CMS. For example, a content creator can submit a story, but it is not published until the copy editor cleans it up and the editor-in-chief approves it.

Document management: CMS software may provide a means of managing the life cycle of a document from initial creation time, through revisions, publication, archive, and document destruction.

Content virtualization: CMS software may provide a means of allowing each user to work within a virtual copy of the entire Web site, document set, and/or code base. This enables changes to multiple interdependent resources to be viewed and/or executed in-context prior to submission.

System Overview:
Looking at system from users perspective, there are three main modules that allow user to administer pages, designs and site data.

Page Management Module: This module allows managing operation on page entity like creating,
editing,and deleting.Here, administrator can add new pages or edit or delete old ones..

Fig. 1: Design and developer view of system

Fig. 2: Page Life Cycle The figure 2 depicts page life cycle:
i) Create page is created by giving it specific title ii) Settings page type is selected, Meta tags texts are provided iii) Edit page text, image and files are managed iv) Preview page is previewed after editing v) Publish page has to be published before user can see it. User will not be able to view pages that are not published vi) Archive after page life time expires, page has to be moved to archive vii) Delete page can either be deleted without being moved to archive or it can be deleted manually later after being moved to archive.

Designs Management Module: This module helps in managing designs for the WCMS. Designs can
be added, updated and deleted under this module.

Site Management Module: Basic site related configuration is managed using this module. The
configuration may include site title, maximum number of pages allowed etc.

System Implementation:
From developers perspective, the system can be divided into two subsystems site administration subsystem and site view subsystem. For a WCMS, site administration subsystem is basic system to be focused upon since we try to facilitate administrator by providing with WCMS to easily manage site

content. And WCMS view that the user gets should precisely match administrators requirements and settings. Here, I briefly describe the procedures to build system from these two different points of view.

Site Administration Subsystem: On administrator side functionality is divided into three modules:
Page management module: This module is responsible to manage following things: i) Creating page by getting page title from administrator. ii) Editing page settings like page type, title tag, Meta keywords, and Meta description. iii) Editing page contents like images, files, and text.

Site management module: Basic site data such as site title, SMTP server, maximum allowed number
of pages, and Meta data are managed using this module.

Design management module: This module lets us have dynamic designs for the site. To store and
change different designs dynamically, the system keeps design data in tables inside database and the design that is selected as default design is loaded when the page loads. For this module to work, the system requires user/administrator to upload a zip file which contains html design page and related resource files. Then the system has to read in html file to store inside database.

Site View Subsystem: Once the administrator has added design and pages to site, site view subsystem
should be able to show the page as the administrator expects it to be. The system first has to load and set default design of the site and then to load page content for that particular page.

Software Modules:
GUI Module (Using Java Application & Swing) Server Side Data Library Design (Using Java Class Library) Server Side Database Management (Using Serialized Objects) Core Website Static Skeleton (Using HTML) Core Website Dynamic Skeleton (Using JavaScript) Webpage Composition/Parsing (Using Java I/O) Local Web Site Generation Module (For analysis and viewing final output) Activity Log (Database) Authentication Module (Administrator Authentication) Website Uploading Module (Using Apache Commons Net Library)

System Requirement:
Software Interface
Language: Java or ASP.NET Microsoft Windows XP or Vista

Hardware Interface
CPU requirement 1. 512mb RAM 2. Processor P4 3. Hard disk 40GB

Application
A CMS-backed (or static) website with institutional information and a link into the digital library system. The digital library system, completely independent of the website. With a different look and feel, and rarely customized beyond the basics, as most Web designers are not able to re-skin arbitrary web applications.

Conclusion:
WCMS users not always need complex functionality from their system. Especially in the case of nave computer users, they only require a basic set of options to manage their site. By providing only this basic set of options or functions, a WCMS can be made more simple and usable for nave kind of computer users. Also there should be a way to easily upload and save many designs and later switch between them. This way WCMS can be made dynamic not only in the sense of page content but in the sense of designs as well. The proposed system is yet another Web content management system to provide user with these two functionalities. Simplicity in managing page content and simplicity in managing site designs are core targets of proposed system.

References:
1. Design and Development of a Web Content Manegement System -Amjad Farooq, 2Mahwish Fatima and 3Abuzar Fahim Department of Computer Science and Engineering, University of Engineering and Technology, Lahore-Pakistan 2. Kowalski, Michael. Evaluating CMS usability: a checklist. Kitsite. [Online] September 23, 2002. http://www.kitsite.com/articles/cms-usabilitychecklist.html.

Group Members:
SR No Name Roll No. Sign

1. 2. 3. 4.

Manisha Ahirrao Dipali Surana Neha Tiwari Madhuri Unde

4 66 68 69