All replies

• 

  

  0

  Sign in to vote

  Today, Web sites are a critical part of business, and the tools to create and deploy Web sites are becoming more flexible and easier to use. However, the production of complicated Web applications that require more than the standard methods of interaction (such as blogs) is not trivial. Often, each application within an organization can require customization.

  In this series we use a fictitious organization, International Business Council (IBC), to show you how to more effectively maximize your Web site capabilities. IBC connects its employees with external business partners in a collaborative community; however, the existing Web site is not meeting their current business needs, and the site must be redesigned. The new, customized Web site must have document storage, discussion groups, specialized workgroups, conference scheduling, schedule session descriptions, session expiration, and other tasks.

  The users' role is to enhance the offerings of the company by improving strategic and tactical decisions. The user community is organized around core issues of workgroups. The community meets face-to-face several times a year in a conference setting. At the conference, issues are identified and then resolved between meetings. The Web site is used to provide information about the community's activities, such as conferences, and as a way to track progress about issues raised at the meetings.

  The existing Web site is based on a document repository that provides a way to exchange documents and update the members about upcoming events. However, the Web site is inadequate for promoting community interaction, especially in the context of Web 2.0 sites with enhanced capabilities such as Weblogs, discussion groups, RSS feeds, and so on. The team's goal is to encourage the community's interaction and provide a publishing framework to support the community activities.

  Tuesday, May 15, 2007 9:37 AM
• 

  

  0

  Sign in to vote

  
  

  Since this is going to be a secure Web site, we need session management to support expiration and acknowledgement of a terms and conditions document before access can be granted. We also want to support a direct manipulation approach to content editing -- if there is an action to take on a piece of content, we want that interaction control to be placed next to the content it affects.

  Other issues with the existing Web site are based on inconsistent visual language, navigation, and information architecture. Content is often hidden within the documents that are placed in the repository; there is no indication of what is in the document until you download and view it. As a result of our analysis, the team decided that the model of a document repository was the wrong model to enforce. We want a content management system to do much more than that.

  Tuesday, May 15, 2007 9:39 AM
• 

  

  0

  Sign in to vote

  
  

  There are many ways to manage your Web site content, from the simple Web log (blog) engine system that allows limited content publishing to a full content management system framework to application frameworks, on which you can build your own custom content management system. With the wide array of choices in the open source space, it can be hard to choose the right solution for your needs.

  Ultimately, we chose Drupal. However, it is useful to describe the rationale for our decision. The next section describes some of the candidate systems, including:

  Drupal,

  Mambo,

  Typo3,
  

  Ruby on Rails,
  

  Movable Type,
  

  WordPress, and
  

  TextPattern.

  Tuesday, May 15, 2007 9:41 AM
• 

  

  0

  Sign in to vote

  Now I will post a brief discription about all the above mentioned Technologies, but only after you have read this much and are now interested in knowing about them... so just tell me when you want me to add more stuff....
  

  Tuesday, May 15, 2007 9:43 AM
• 

  

  0

  Sign in to vote

  Really good stuffs m8. Hope others like it as i did. Good info.
  

  Tuesday, May 15, 2007 10:26 AM
• 

  

  0

  Sign in to vote

  Yes, the content certainly seems to be interesting and lucrative. Thanks for starting the post and sharing such info.

  Please give us more details on Content Management, its scope, application areas, technologies being used etc.

  Tuesday, May 15, 2007 11:54 AM
• 

  

  0

  Sign in to vote

  Rocking info Varun.

  Well i am sure we are all eager to try out our hands on CMS. So i suggest you have a look at Joomla. Is a free Open source Content Management System available at http://www.joomla.org

  Just go to www.007ihost.com and get an account. And use the script installer in the admin to install Joomla. Please note that you will have to create a database and a user in the admin panel of 007ihost.com

  Just try out Joomla. And if you are satisfied with the service of 007ihost, then just buy a domain and you are ready with your very own CMS website.

  If you need any more help from my side, please let me know.

  Tuesday, May 15, 2007 7:29 PM
• 

  

  0

  Sign in to vote

  As Adnan has given a description about Joomal, i will give a short description of other systems... then we will see which one is better and discuss more in detail regarding them...
  

  Wednesday, May 16, 2007 11:45 AM
• 

  

  0

  Sign in to vote

  Drupal

  "Drupal is software that allows an individual or a community of users to easily publish, manage and organize a great variety of content on a Web site. Tens of thousands of people and organizations have used Drupal to set up scores of different kinds of Web sites, including:

  • Community Web portals and discussion sites
  • Corporate Web sites/intranet portals
  • Personal Web sites
  • Aficionado sites
  • E-commerce applications
  • Resource directories

  Drupal includes features to enable content management systems, blogs, collaborative authoring environments, forums, newsletters, picture galleries, file uploads and download, and much more. Drupal is open source software licensed under the GPL and is maintained and developed by a community of thousands of users and developers. Drupal is free to download and use." (Source: CMS Matrix)

  Drupal is a relative youngster compared to other content management systems (CMSs). However, we got the impression the framework was well written, robust, very extensible, and seemed to have a thriving development community that was generating a lot of adoption and support.

  As with other CMSs, the framework was very extensible. Many of the features we needed were provided as modules that could easily be snapped into the core functions of our Web site.

  The framework and templating (theming) system are all written in PHP; there is no separate tag language to be learned. If you need to break out of the framework, it is very easy to do. (Of course, this isn't recommended, but it does offer ultimate flexibility.)

  Session management is built into the core functions, which was more than other CMSs provided. This could help us pass some hurdles later on.

  Drupal is known for scalability, or ease of growing a Web site from a small set of users to an enterprise level. The framework also has the ability to 'throttle' areas of the site that could cause potential problems during heavy traffic situations.

  There is still an apparent learning curve to the "Drupal Way" of creating sites, but significantly less compared with other CMSs. The ability to use PHP to move freely between the business logic layer and the presentation layer (using the PHP template engine) was also very appealing.

  We'd heard that the access control of Drupal can be more granular, but figured we could deal with that using the flexible extensibility. Drupal 5 has just been released with many enhancements to Version 4.7.

  Wednesday, May 16, 2007 11:48 AM
• 

  

  0

  Sign in to vote

  
  

  "Mambo Open Source is one of the finest open source content management systems available today. The default installation of Mambo is easy to set up and easy to maintain. The setup utility uses a 4-step wizard interface that allows you to install the entire system without the need of advanced technical knowledge. Once installed, the system includes a variety of templates that you can choose from and a large number of functions that are ready to go. Content can be added, edited, and manipulated without having to know HTML, XML, or DHTML -- just enter your content using a friendly editor and click Publish. More advanced users are able to control the system to a level that suits their skills. The core files are written in PHP [Mambo is based on Linux™, Apache, MySQL, P for PHP, Perl and Python (LAMP)] and can be modified easily. The system is robust, proven, and backed by a large community of users and professional developers. (As of early 2006, Mambo is five years old!)" (Source: CMS Matrix)

  At the time, Mambo was popular and seemed to offer a very easy install and an attractive, easy-to-use administration interface. Usually disregarded, the back end of a CMS becomes very important if you need it to work well for clients who need to administer the Web site after you hand it off.

  The easy installation seemed to get us to a point where almost all the function we needed was available and ready to be themed. However, as with many CMSs, the templating is limited to a tag system that leaves you at the mercy of the quality of the markup that is substituted for the tags. This is fine if the markup is valid, semantically structured, and adequately sprinkled with CSS ID and class attributes to aid styling. If it isn't, then you can find yourself delving into the guts of the application to figure out how to correct the generated output.

  Mambo also offered limited session management, although it was still more than other CMSs offer.

  The development path seemed confusing, and the future of this solution was not certain to us. Mambo's development track is divided into several solutions. Miro is a commercial product and Joomla seems to be a new CMS spawned from Mambo. Mambo still exists and its current development path seems to be more stable.

  Wednesday, May 16, 2007 11:49 AM
• 

  

  0

  Sign in to vote

  
  

  "TYPO3 is an enterprise-level open source content management system released under the GPL. It runs on more than 122,000 servers worldwide. The application has been translated into 43 languages and is actively being developed in a community of over 27,000 users in 60 countries. Some of its users include BASF, DaimlerChrysler, EDS, Konika-Minolta, Volkswagen, UNESCO, as well as numerous universities, government agencies, and nonprofit organizations." (Source: CMS Matrix )

  Typo3 is big. Big application. Big community. Big adoption. Big list of extended features and contributions. The learning curve is big, too. There is no doubt that Typo3 could do all we required, but there seemed to be other issues in addition to complexity.

  The markup generated by a lot of the core and contributed modules used structure from the mid to late '90s, with lots of table layouts, not much use of effectively placed CSS ID and class attributes, and sometimes invalid structure. We wanted to use current best practices to keep our development iterations flexible, so this wasn't going to help timely development. The templating system also seemed very complex compared to other solutions. The time invested in understanding how to theme the Web content outweighed the power of the templating system.

  The administrative interface felt awkward and old, especially compared to Mambo. This was an important consideration, because we needed to hand off the eventual administration of the site.

  If we'd had more time, Typo3 might have been an option. But, it seemed like it needed a rewrite to keep it fresh and competitive with other CMS that are emerging. It appears that the issue of using standards based xHTML and CSS is being addressed in the new version of Typo3.

  Wednesday, May 16, 2007 11:50 AM
• 

  

  0

  Sign in to vote

  
  

  "Ruby is a pure object-oriented programming language with a super clean syntax that makes programming elegant and fun. Ruby successfully combines Smalltalk's conceptual elegance, Python's ease of use and learning, and Perl's pragmatism. Ruby originated in Japan in the early 1990s and has started to become popular worldwide in the past few years as more English language books and documentation have become available. Rails is an open source Ruby framework for developing database-backed Web applications. Rail's guiding principles: less software and convention over configuration. Less software means you write fewer lines of code to implement your application. Keeping your code small means faster development and fewer bugs, which makes your code easier to understand, maintain, and enhance. You will see how Rails cuts your code burden shortly.

  Convention over configuration means an end to verbose XML configuration files -- there aren't any in Rails! Instead of configuration files, a Rails application uses a few simple programming conventions that allow it to figure out everything through reflection and discovery. Your application code and your running database already contain everything that Rails needs to know!" (Source: Rolling with Ruby on Rails)

  Typical content management systems allow authenticated users to create content forming pages as part of a Web site. Ruby On Rails (ROR), however, does not provide this out of the box. It provides a Web application framework. Using ROR, you can build a custom CMS from scratch.

  At the time of our project, there was a huge buzz around ROR, mainly promoted by 37Signals and its impressive array of real online ROR applications such as Base Camp.

  We liked the way the bindings to the database through the framework lived up to the hype. These did help speed up those repetitive parts of development that hook to your database table columns.

  At the time of our investigation, the framework was somewhat blog centric. Stability was an issue, but we recognized its potential for use on future projects.

  Creating a custom CMS has its appeal. For example, with a custom solution we could have created a themable administrative interface. But, given our time restrictions, we needed a CMS framework to build on.

  Wednesday, May 16, 2007 11:52 AM
• 

  

  0

  Sign in to vote

  
  

  We considered using an existing publishing system that principally supported the creation of blogs. We've previously used such systems to support content for non-blog Web sites by redefining the way categories and data are used. These types of solutions are not aligned to compete with the likes of Drupal, Mambo, and Typo3. For example, session management as provided by Drupal and Typo3 is not typically supported. However, they do provide a very simple and quick way of creating a simple CMS.

  Given that these solutions are blog centric, here are some alternatives:

  
  

  Movable Type

  "Movable Type is a powerful and customizable publishing platform allowing users to create attractive, expressive Weblogs within a personal publishing system that is infinitely customizable and versatile. Running as server-based software, Movable Type has been adopted by individuals and corporations who are drawn to its depth of features, open architecture, and robust library of third-party plug-ins designed to extend the system's functionality. Building from the current base of hundreds of plug-ins created by dedicated developers around the world, an entirely new class of applications can be built on top of the familiar and tested Movable Type system." (Source: CMS Matrix)

  One of the more popular blog publishing systems at the time, this Perl implementation has a large community of contributors and a good support structure. The immediate roadblock was the creation of a charging structure by the makers, Six Apart, to support the development of its product. Because we were trying to create an open source solution, this nipped the idea of using Movable Type in the bud.

  
  

  WordPress

  "WordPress is a state-of-the-art, semantic personal publishing platform with a focus on aesthetics, Web standards, and usability. What a mouthful. WordPress is both free and priceless at the same time. More simply, WordPress is what you use when you want to work with your blogging software, not fight it. WordPress' default capabilities can be increased many fold (and new functions can be easily added) through its easy-to-use, plug-in architecture." (Source: CMS Matrix)

  WordPress was growing in stature at the time of our project. Similar to Drupal, the wiki-style documentation system supporting this solution is useful. The core code is clean and easy to extend, and the user interface is very easy to use.

  The templating system is a typical tag-based system, which compared well with other blog publishing platforms. The generated output from the system supported current best practices, and made the development of content layout and accessibility much easier.

  One shortfall of WordPress is its lack of caching capabilities, which we thought would limit scalability.

  
  

  TextPattern

  "A free, flexible, elegant, easy-to-use content management system for all kinds of Web sites, even Weblogs. When it comes to publishing on the Internet, beginners and experts alike are met with a bothersome paradox: word processors and graphics applications allow anyone to do a pretty good job of managing text and images on a personal computer, but to make these available to the worldwide Web -- a seemingly similar environment of documents and destinations -- ease of use vanishes behind sudden requirements for multilingual programming skills, proficiency in computer-based graphic design, and, ultimately, the patience of a saint. Those who soldier on anyway may find themselves further held back by the Web's purported inflexibility with written language, with its reluctance to cope with all but the plainest of text, or by the unpredictable results brought about by using WYSIWYG Web editors. TextPattern is a Web application designed to help overcome these and other hurdles to publishing online, and to simplify the production of well-structured, standards-compliant Web pages." (Source: CMS Matrix)

  Like WordPress, TextPattern looked like another well-crafted blog publishing system. It has a clean administrative interface and seems easy to use. However, it lacks a lot of the features we were looking for, including session control and caching.

  Wednesday, May 16, 2007 11:54 AM
• 

  

  0

  Sign in to vote

  The following image link gives the details of the software requirements of the above systems...
  
  http://www-128.ibm.com/developerworks/ibm/library/i-osource1/cms_requirements.gif
  

  Wednesday, May 16, 2007 11:59 AM
• 

  

  0

  Sign in to vote

  Really good research and information Varun.
  
  Good work. We now have few people who really want to contribute to the forums and that too consistently.
  

  Wednesday, May 16, 2007 12:06 PM
• 

  

  0

  Sign in to vote

  One of the main constraints in Content Management Document Management. The criteria to be considered here are the standardisation of the way in which content is stored and retrieved. For a web based CMS, the emphasis is on  XSLT-based CMS [ XSLT: Extensible Stylesheet Language Transformations (XSLT) is an XML-based language used for the transformation of XML documents. XSLT is designed to transform XML documents into other XML documents. The original document is not changed; rather, a new document is created based on the content of an existing one.^[2] The new document may be (output) by the processor in standard XML syntax or in another format, such as HTML or plain text.^[3] XSLT is most often used to convert data between different XML schemas or to convert XML data into HTML or XHTML documents for web pages, or into an intermediate XML format that can be converted to PDF documents.], that can compile ready documents from XML data and XSLT-template. e.g a Report Generated by BIRT Tool of Eclipse might need to be converted into a report with the same format but comaptible with another reporting tool.

  Another important criteria in Content Management is about understanding the content of documents, through analysis of semantics(meanings) of words in the document for intelligent clustering and labelling of these documents for faster and more effective search. e.g The search string "Agreement on Agriculture", should give documents speaking about WTO standards on Agriculture and not blindly return terms containing the words 'Agreement' and 'Agriculture'. This is achieved by setting up a semantic web and the use of thesaurus and ontologies containing the phrases and words used in domains relevant to the document as well as the different semantic relations between these words and phrases.e.g WordNet is a popular Ontology consisting of all the generally used words in English Language.

  Wednesday, May 16, 2007 12:41 PM
• 

  

  0

  Sign in to vote

  Content management, or CM, is a set of processes and technologies that support the evolutionary life cycle of digital information. This digital information is often referred to as content or, to be precise, digital content. Digital content may take the form of text, such as documents, multimedia files, such as audio or video files, or any other file type which follows a content lifecycle which requires management.

   

  The process of content management

  The digital content lifecycle consists of six primary phases: create, update, publish, translate, archive and retire. For example, an instance of digital content is created by one or more authors. Over time that content may be edited. One or more individuals may provide some editorial oversight thereby approving the content for publication. Publishing may take many forms. Publishing may be the act of pushing content out to others, or simply granting digital access rights to certain content to a particular person or group of persons. Later that content may be superseded by another form of content and thus retired or removed from use.

  Content management is an inherently collaborative process. It often consists of the following basic roles and responsibilities:

  • Content author - responsible for creating and editing content.
  • Editor - responsible for tuning the content message and the style of delivery, including translation and localization.
  • Publisher - responsible for releasing the content for use.
  • Administrator - responsible for managing access permissions to folders and files, usually accomplished by assigning access rights to user groups or roles. Admins may also assist and support users in various ways.
  • Consumer, viewer or guest- the person who reads or otherwise takes in content after it is published or shared.

  A critical aspect of content management is the ability to manage versions of content as it evolves (see also version control). Authors and editors often need to restore older versions of edited products due to a process failure or an undesirable series of edits.

  Another equally important aspect of content management involves the creation, maintenance, and application of review standards. Each member of the content creation and review process has a unique role and set of responsibilities in the development and/or publication of the content. Each review team member requires clear and concise review standards which must be maintained on an ongoing basis to ensure the long-term consistency and health of the knowledge base.

   

  A Content Management System (CMS) is a software system used for content management. This includes computer files, image media, audio files, electronic documents and web content. The idea behind a CMS is to make these files available inter-office, as well as over the web. A Content Management System would most often be used as archival as well. Many companies use a CMS to store files in a non-proprietary form. Companies using a CMS file share with ease, as most systems use server based software, even further broadening file availability. As shown below, many Content Management Systems include a feature for Web Content, and some have a feature for a "workflow process."

  "Workflow" is the idea of moving an electronic document along for either approval, or for adding content. Some Content Management Systems will easily facilitate this process with email notification, and automated routing. This is ideally a collaborative creation of documents. A CMS facilitates the organization, control, and publication of a large body of documents and other content, such as images and multimedia resources.

  A web content management system is a content management system with additional features to ease the tasks required to publish web content to web sites.

  Web content management systems are often used for storing, controlling, versioning, and publishing industry-specific documentation such as news articles, operators' manuals, technical manuals, sales guides, and marketing brochures. A content management system may support the following features:

  • Import and creation of documents and multimedia material
  • Identification of all key users and their content management roles
  • The ability to assign roles and responsibilities to different content categories or types.
  • Definition of the content workflow tasks, often coupled with event messaging so that content managers are alerted to changes in content.
  • The ability to track and manage multiple versions of a single instance of content.
  • The ability to publish the content to a repository to support access to the content. Increasingly, the repository is an inherent part of the system, and incorporates enterprise search and retrieval.
  • Some content management systems allow the textual aspect of content to be separated to some extent from formatting. For example the CMS may automatically set default color, fonts, or layout.

  Forms

  Content management systems take the following forms:

  • a web content management system is software for web site management - which is often what is implicitly meant by this term
  • the work of a newspaper editorial staff organization
  • a workflow for article publication
  • a document management system
  • a single source content management system - where content is stored in chunks within a relational database.^[1]

  Web content management systems

  A web content management system is a computer 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 Web CMS provides the following key features:

  Automated templates

  Create standard visual templates that can be automatically applied to new and existing content, creating one central place to change that look across a group of content on a site.

  Easily editable content

  Once your content is separate from the visual presentation of your site, it usually becomes much easier and quicker to edit and manipulate. Most CMS software include WYSIWYG editing tools allowing non-technical individuals to create and edit content.

  Scalable feature sets

  Most CMS have plug-ins or modules that can be easily installed to extend an existing site's functionality.

  Web standards upgrades

  Active CMS solutions usually receive 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 submits a story but it's not published on the website until the copy editor cleans it up, and the editor-in-chief approves it.

  Document management

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

  History

  The term Content Management System was originally used for website publishing management systems. Early content management systems were developed internally at organizations which were doing a lot of web publishing, such as on-line magazines, newspapers, and corporate newsletters. In 1995, CNET spun out its internal web document management and publication system into a separate company called Vignette, which opened up the market for commercial content management systems.

  As markets evolved, the scope of products promoted as content management systems greatly broadened, fragmenting the meaning of the term. Wiki systems and web-based groupware are often described as content management systems, in contrast to the original website publishing management system definition.

  Operation

  A web site content management system often runs on the website's server. Most systems provide controlled access for various ranks of users such as administrators, copy editors, senior editors, and content creators. Access is usually via a web browser program, possibly combined with some use of FTP for uploading content.

  Content creators submit their documents to the system. Copy editors comment on, accept, or reject documents. Layout editors lay out the site. The editor in chief is then responsible for publishing the work to the live site. The content management system controls and helps manage each step of this workflow, including the technical task of publishing the documents to one or more live web servers.

  The content and all other information related to the site is usually stored in a server-based relational database system. The content management system typically keeps a record of previous website editions and in-progress editions.

  The pages controlled and published through the content management system can then be seen by the visitors to the website.

  In larger organizations these server based documents need to communicate with desktop applications and Open Document Management APIs perform the necessary "translations". They have made substantial cost and time savings to document management overall, and assist in smooth flow of documents through enterprises, applications and processes.

  Lately CMS systems have been associated with CRM, Customer Relation Management or Constituent Relationship Management, software programs. Because of that some software companies are beginning to create software platforms that bundle CMS and CRM functions[1].

  Terminology

  The following terms are often used in relation to web content management systems but they may be neither standard nor universal:

  Block

  A block is a link to a section of the web site. Blocks can usually be specified to appear on all pages of the site (for example in a lefthand navigation panel) or only on the home page.

  Module

  A content module is a section of the web site, for example a collection of news articles, an FAQ section, etc. Some content management systems may also have other special types of modules, for example administration and system modules.

  Theme

  A theme specifies the cosmetic appearance of every page of the web site, controlling properties such as the colours and the fonts.

  Types of CMS

  Module-based CMS

  Most tasks in a document's life-cycle are served by CMS modules. Common modules are document creation/editing, transforming and publishing.

  TODDS CMS

  TODDS is a system that was created to counteract the MOSS System. It is an acronym that stands for Totally Organic Data Driven System. It is a new tool that is helping IT departments do their jobs more efficiently, especially when they should belong in a Marketing type organization.

  Document transformation language-based CMS

  Another approach to CMS building with use of open standards. XSLT-based CMS compile ready documents from XML data and XSLT-template. XML Sapiens-based CMS compile a document from the stream of ‘pure’ data, design template and functionality templates.

  Web-based CMS

  Another approach to CMS building uses databases such as PostgreSQL, MySQL or MS SQL, and scripting languages or tools such as ColdFusion, PHP, jsp or ASP to interact with the data to parse them into visual content. Data stored in a database are queried and compiled into html pages or other documents and transformed using cascading style sheets. These systems can include a number of other functions, such as discussion boards, blogs, or email newsletters.

  This is a list of notable content management systems that are used to organize and facilitate collaborative content creation. Many of them are built on top of separate content management frameworks.

   

   

  Name	Platform	Supported databases	Latest stable release	License
  ActionApps	PHP	MySQL	2.8.1	GPL
  Alfresco	Java	MySQL, Oracle, SQL Server, PostgreSQL	2	GPL
  Apache Lenya	Java, XML, Apache Cocoon		1.2.4	Apache License
  Aukyla SiteManager	PHP5, Aukyla Platform	PostgreSQL	1.1	GPL
  BLOG:CMS	PHP	MySQL		GPL
  blosxom	Perl	Flat-file database	2.0	MIT
  Caravel CMS	PHP	OpenLDAP and PostgreSQL		GPL
  CMScout	PHP	MySQL	1.23	GPL
  CMSimple	PHP	Flat-file database		Affero
  CMS Made Simple	PHP	MySQL/Postgresql	1.0.5	GPL
  CorneliOS	Perl	MySQL and any Perl DBI, filesystem	0.7.4	GPL
  Cyclone3	Perl, XUL, JavaScript, C, Java	MySQL and any Perl DBI	3.0	GPL
  Daisy	Java, XML, Apache Cocoon	MySQL	2.0.1	Apache License
  Dokuwiki	PHP	Flat-file database	2006-11-06	GPL
  DotNetNuke	VB.NET	Microsoft SQL Server	4.5.1	BSD
  Dragonfly CMS	PHP	MySQL/PostgreSQL	9.1.2.1	GPL
  Drupal	PHP	MySQL/PostgreSQL	5.1	GPL
  e107	PHP	MySQL	0.7.8	GPL
  eGroupWare	PHP	ADOdb		GPL
  Enano CMS	PHP	MySQL		GPL
  Epiware	PHP	MySQL	4.5	GPL
  Etomite CMS	PHP	MySQL	0.6.1.3	GPL
  eZ publish	PHP (PHP4 Only)	MySQL/Postgresql/Oracle	3.9.0	GPL
  Fedora	Java	MySQL or Oracle		Educational Community License
  Geeklog	PHP	MySQL	1.4.0	GPL
  Hello! CMS	PHP	Flat-file database	0.0.7	GPL
  Jahia	Java	HyperSonic SQL/MySQL/PostgreSQL/Oracle/SQL Server	5.0	Custom
  jAPS - java Agile Portal System	Java, XML on Windows or Linux	HyperSonic SQL, PostgreSQL		GPL
  Jaws Project	PHP	MySQL, PostgreSQL, MSSQL, SQLite	0.7.1	GPL
  Joomla!	PHP	MySQL	1.0.12	GPL
  JMDCMS	Asp.net, C#	Microsoft SQL Server	3.0.0.2	OpenSource
  KnowledgeTree Document Management System	PHP	MySQL	3.3.1	KPL (custom)
  Krang CMS	Perl on mod_perl	MySQL	2.008	BSD
  Lyceum	PHP	MySQL		GPL
  Magnolia	Java	Content repository API for Java (JSR-170)	3.01	LGPL
  Mambo	PHP	MySQL	4.6.1	GPL
  MediaWiki	PHP	MySQL, PostgreSQL	1.9.3	GPL
  Midgard CMS	PHP (Midgard framework)	MySQL		LGPL
  MKPortal	PHP	MySQL	1.1	custom
  MMBase	Java	MySQL/PostgreSQL		MPL
  MODx	PHP	MySQL	0.9.5	GPL
  Muse	PHP	MySQL	1.0	BSD
  Nucleus CMS	PHP	MySQL	3.23	GPL
  Nuke-Evolution	PHP	MySQL	2.0.2	GPL
  Nuxeo CPS	Zope	ZODB	3.4.3	GPL
  ocPortal	PHP	MySQL		custom
  OpenACS	TCL AOLserver	PostgreSQL/Oracle	5.1.5	GPL
  OpenCms	Java	MySQL, Oracle	6.2.3	LGPL
  OpenPHPNuke	PHP	MySQL, PostgreSQL, SQLite	2.4.3	GPL
  phpCMS	PHP	Flat-file database	1.2.2	GPL
  PHP-Fusion	PHP	MySQL	6.01.10	GPL
  PHP-Nuke	PHP	MySQL	8.0	GPL
  phpWCMS	PHP	MySQL		GPL
  phpWebSite	PHP	MySQL or PostgreSQL	1.1.0	LGPL
  PhpWiki	PHP	Flat-file database/MySQL/PostgreSQL etc.		GPL
  Pivot	PHP	Flat-file database	1.30	GPL
  Plone	Zope, Python	ZODB, MySQL & PostgreSQL via Zope	2.5.2	GPL
  PmWiki	PHP	Flat-file database		GPL
  PostNuke	PHP	MySQL	.764	GPL
  PuzzleApps	PHP, XML, XSLT	MySQL, PostgreSQL, SQLite, MSSQL	2.2	LGPL
  Scoop	Perl on mod_perl	MySQL	1.1.8	GPL
  SilverStripe	PHP	MySQL	2.0.0	BSD
  SiteFrame	PHP + Smarty	MySQL	5.0.2	Creative Commons
  Slash	Perl on mod_perl	MySQL		GPL
  SPIP	PHP	MySQL	1.9.2	GPL
  SpotlightPHP	PHP + MySQL	MySQL	2.0.0	Creative Commons
  Textpattern	PHP	MySQL	4.0.4	GPL
  TikiWiki	PHP	ADOdb		LGPL
  TribalCMS	PHP	MySQL	5.0.0	GPL
  TWiki	Perl	Perl DBI compatible	4.0.4	GPL
  Typo	Ruby on Rails	MySQL, PostgreSQL, SQLite		MIT
  TYPO3	PHP	MySQL, PostgreSQL, Oracle	4.1.1	GPL
  TYPOlight	PHP	MySQL, PostgreSQL, Oracle, MSSQL	2.2.12	GPL
  UNITED-NUKE	PHP	MySQL, DB2, PostgreSQL, MSSQL, SQLite	4.2.07ms2	GPL
  WebGUI	Perl on mod_perl	MySQL		GPL
  Website Baker	PHP	MySQL	2.6.5	GPL
  Xaraya	PHP with XHTML/XML/XSLT	MySQL, PostgreSQL, SQLite using ADOdb and Microsoft SQL Server with Creole	1.1.2	GPL
  XOOPS	PHP	MySQL	2.2	GPL

  Freeware

  This section lists freeware software that is available at no cost, but is neither free nor open source.

  Name	Platform	Supported databases	Latest stable release	Online Demo
  Blockstar	Java			Yes
  CivicSpace	PHP	MySQL	0.8.3
  FlexCMS	ASP.NET	SQL Server	1.0
  Movable Type	Perl	MySQL or MS SQL server or Oracle or PostgreSQL or SQLite	3.35	Yes

  Commercial, Rental (ASP/ PHP / SaaS)

  Name	Supported browsers for management	Latest stable release	Price in USD / month	Online Demo
  Pepperio	Internet Explorer and Firefox	4.4	from $149	Yes

  Commercial, Low Cost (< $5,000)

  Name	Platform	Supported databases	Latest stable release	Price in USD	Online Demo
  Accrisoft Freedom	PHP	MySQL	5.7	$50 / month	Yes
  Community Server	ASP.NET	SQL Server	2007	$300	Yes
  Edit-X CMS	PHP	MySQL	2007	from $195	Yes
  iWebex CMS	PHP	MySQL	1.0	from $2999	Yes
  TribalCMS ProLite, Pro and Enterprise	PHP	MySQL	5.0.0	from ~$500	Yes
  WebHat	PHP	MySQL, Oracle, SQL Server	4.3.20	from $1000	Yes

  Commercial, Medium Cost ($5,000 - $15,000)

  Name	Platform	Supported databases	Latest stable release	Price in USD	Online Demo
  Agility CMS	ASP.NET	SQL2K	2.3	$300 - $1000 per month	Screenshots
  Jalios JCMS Starter Edition	Java		5.6.1		Yes
  Simplicis	JSP	Any SQL-92	3.0.2	$5,999/year	Yes
  Traction TeamPage	Java	Built-in	3.7	$5,000 and up
  WebDeck	Java	MySQL, MS SQL Server, Oracle	6.0	$19,000/year	Yes
  WebImpetus	MacOS and Windows	4th Dimension		£1,000 per year

  Commercial, High Cost (> $15,000)

  Name	Platform	Supported databases	Latest stable release	Price in USD	Online Demo
  CoreMedia CMS	Java	Oracle, IBM DB2, Microsoft SQL Server	CoreMedia CMS 2006
  Documentum (owned by EMC)	Java	Oracle, Microsoft SQL Server, IBM DB2	5.3sp4
  EM3 iOn	Java	Microsoft SQL Server, Oracle	5.4		Yes
  EPiServer	C# / ASP.NET 2.0	Microsoft SQL Server, Oracle	4.61	Around $20,000	Yes
  FatWire	Java	Oracle, Microsoft SQL Server, IBM DB2, Sybase, MySQL	Content Server 7.0		Yes
  FileNet (owned by IBM)	Java	Oracle, Microsoft SQL Server, IBM DB2	Content Manager 4.0
  Jadu	PHP and .NET	MS SQL Server, MySQL	2.0x
  Jalios JCMS	Java/J2EE		5.6.1		Yes
  Livelink ECM	J2EE	Oracle Database or MS SQL Server	9.7	price per named users	Yes
  Microsoft Office SharePoint Server	.NET	Microsoft SQL Server (2000 or 2005), SQL Express	2007		No
  RedDot CMS (owned by Open Text)	Windows	MS SQL Server, Oracle Database	7.1	price per CPU or named users	Yes
  Rhythmyx	XML, J2EE	Oracle database or MS SQL Server	6.0	Starts at $90,000; multi-site enterprise is $250,000	No
  Socialtext	Perl
  Stellent (owned by Oracle)	Java, IDocScript, XML	Oracle, SQL Server, other	7.5
  Vignette Content Management	Java	Oracle Database, MS SQL Server, IBM DB2	7.3.1
  VYRE	J2EE	All supported by Hibernate	4.2.1

  Unclear licensing conditions

  The vendors of this software do not disclose prices or licensing details, requesting to contact for this information individually

  Name	Platform	Supported databases	Latest stable release
  Aegir	Midgard add-on		1.0.3
  Ariadne		Oracle, PostgreSQL
  Doop (CMS)	PHP	Flat-file database	1.3.5

   

   

  Wednesday, May 16, 2007 12:51 PM
• 

  

  0

  Sign in to vote

  OSCOM - The international association for Open Source Content Management

  OSCOM is the international association connecting users and developers of Open Source Content Management solutions.

  OSCOM organizes events, promotes standards and undertakes projects to further the state of the art of Open Source Content Management. OSCOM promotes Open Source Content Management solutions as powerful, affordable and flexible replacements for proprietary products.
  

  OSCOM Sites: OSCOM International, OSCOM Germany.

   

  Also check these links:

   

  http://www.opensourcecms.com

  http://www.la-grange.net/cms

  http://www.opencms.org

  http://ez.no

  http://java-source.net/open-source/content-managment-systems

  http://plone.org/
  

  Wednesday, May 16, 2007 12:59 PM
• 

  

  0

  Sign in to vote

  Damn good informations.
  
  But i guess please just dont copy and paste entire pages from the websites. If you want, then only provide links to that page.
  
  Just copying and pasting the entire pages, is a waste of space and also bandwidth for MS.
  Also it doesn't look good in forums.
  

  Wednesday, May 16, 2007 1:07 PM
• 

  

  0

  Sign in to vote

  Varun, lets do a comparison. Everybody, please vote for your favourite CMS

  Wednesday, May 16, 2007 3:09 PM
• 

  

  0

  Sign in to vote

  Alright people lets do the voting....
  
  I vote for Drupal, I will even post some of its benefits after the voting has been done... people voting their fav Will have to post something about the particular CMS which made them select the particular one...
  

  Friday, May 18, 2007 3:33 AM
• 

  

  0

  Sign in to vote

  Sorry my friend, i dont know much about this topic so i cant vote. But yes i am eager to see the results and see which one is the fav. amongst the student rockstars
  

  Friday, May 18, 2007 5:55 AM
• 

  

  0

  Sign in to vote

  i must say that its a really  very good thread on CMS....

  Friday, May 18, 2007 1:10 PM
• 

  

  0

  Sign in to vote

  I vote for Joomla. Apart from having support of tons of themes and skins, the interface is easy to understand and use. The disadvantage will Joomla, is that i am finding very hard to locate and edit information in the php file. After all, whats the use of open source, if you cant use the source???

  Friday, May 18, 2007 6:00 PM
• 

  

  0

  Sign in to vote

  Looks like we are out of people to get a voting.. so lets do it this way, I m posting some more specific stuff regarding Drupal, and you post some for Joomla, its a race between Drupal and Joomal, so lets see which one wins the race...
  

  Saturday, May 19, 2007 11:14 AM
• 

  

  0

  Sign in to vote

  Decision to use Drupal

  Because we needed to make this Web site design easy for ourselves and anyone adopting the solution, the ease of installing the framework and the time it would take to figure out how to use it was a key factor. While Ruby on Rails (ROR) was intriguing, we decided that too much time would be spent writing a CMS from scratch, so ROR was dropped from our consideration.

  If we were to be able to effectively control access to the information for each persona, having robust and flexible session and user management would make our implementation easier. Of course, the speed of implementation would also be improved by having a robust pluggable infrastructure backed up with a vibrant community contributing quality extensions to the existing framework.

  Another key aspect was the potential to ramp up the scalability as the number of concurrent users started to increase.

  The ease of adjusting the way the content was displayed was crucial; we needed to remain flexible during iterations of the design and any future adjustments. This so-called "themability" also was required for using the current best practices of Web design with respect to semantic xHTML, CSS, and accessible design.

  
  

  
  

  
  

  
  

  http://www-128.ibm.com/developerworks/ibm/library/i-osource1/cms_comparison.gif

  shows a comparison of how the candidates met our requirements. It was obvious that we needed something more than the blog engines could provide.

  
  

  
  

  Mambo was very appealing from the ease of install and the UI, but the development track at the time was fractured and didn't give us any confidence of support.

  Typo3 seemed to have a huge community and the maturity we were looking for. However, the learning curve for using Typo3 is daunting in comparison to Drupal.

  We did have to invest some time to learn the Drupal way, and the framework just seemed to make sense. We also felt that Drupal provided the right combination of framework and flexibility to break out of the framework when needed to get the job done. With all things considered, we decided to use Drupal. The landscape of open source CMS is continuously changing, and in the future we'll revisit these and any new entries in the field.

  Saturday, May 19, 2007 11:24 AM
• 

  

  0

  Sign in to vote

  Drupal in detail

  Drupal contains many built-in features and is easily extensible with a vibrant community supporting and adding to the portfolio of additional features. The basic features include:

  • Friendly URLs using Apache's mod_rewrite capability
  • Easily extensible using Drupal's module framework (The community has developed many useful modules that provide functions such as taxonomy display, jabber authentication, private messages, bookmarks, and so on.)
  • A personalization environment for individualized content and presentation based on user preferences
  • Role-based permission system to define access to the viewing and editing of content
  • Content is fully indexed to support search
  • Drupal is written on top of a database abstraction layer, so the framework can be easily extended to other database back ends
  • Support for other content forms such as polls, threaded comments, and discussions and content syndication
  • Separation of content from styling in a templating system that uses HTML, CSS, and PHP
  • Administrative support for logging, analysis, and Web-based administration Online help

  
  

  Extending Drupal

  We used Drupal's module framework to add the extended features we needed to support our Web site. The extended features include:

  • Creating an extranet environment -- a closed access site that requires authentication before seeing any information
  • Session expiration based on user interaction with the Web site
  • A terms and conditions policy implementation
  • An extension of the existing content editing interface to provide "in place" editing (For example, show an authorized user what they can edit in the context of the Web page and allow them to elect to edit that content there and then.)
  • Management of announcements to publicize general information that all members should see
  • Management of working groups mission, current status, action items, and so on
  • Management of the creation of conference sessions and agendas using Ajax to help the administrative interface
  • An extended view and administrative interface for member information and the search of this information
  • Additional blocks of information displayed as a sidebar to display contextual data based on the members role and data they own or create
  • A weekly digest of information e-mailed to members interested in specific areas of content

  
  

  Saturday, May 19, 2007 11:27 AM
• 

  

  0

  Sign in to vote

  Alright time to get some resources...
  
  Get products and technologies
  

  • Drupal: An open source content management system.
    
    
  • MySQL: An open source database store.
    
    
  • PHP: A Web-based language for supporting dynamic content.
    
    
  • PHPMyAdmin: A PHP tool intended to handle the administration of MySQL over the Web.
    
    
  • MySQL Query Browser: A graphical client to work with your MySQL databases and run queries.
    
    
  • MySQL Administrator: A GUI to administer your MySQL Server.
    
    
  • Apache: An open source Web server.
    
    
  • Eclipse: An open source development environment.
    
    
  • CVS: A source code management system integrated into Eclipse to track code changes.
    

  Other CMS Systems...
  

  • Mambo
  • Typo3
  • Ruby on Rails
  • Movable Type
  • WordPress
  • TextPattern

  
  
  

  Saturday, May 19, 2007 11:31 AM
• 

  

  0

  Sign in to vote

  Very good explaination Varun for supporting Drupal. I dont know much so i cant comment on it, but all i am trying to do is trying to just get info about whatever i can see in the posts and conversations. Good thread in all. Lot to learn.
  

  Saturday, May 19, 2007 4:01 PM
• 

  

  0

  Sign in to vote

  Nice info Varun, i will look at Drupal more closely and let you why i think Joomla is better and how Drupal defeats Joomla in features(if any).

  Till then, opensource rules....

  Saturday, May 19, 2007 10:20 PM
• 

  

  0

  Sign in to vote

  well havent tried out either, so cant cast my vote, but i think opensource rules and joomal can be better...anyways

  nice info there guys.....ummm .. i m learning from it...

  Monday, May 21, 2007 11:07 AM
• 

  

  0

  Sign in to vote

  So why not start using it... you need to get this things first
  1.) Drupal
  2.) PHP
  3.) Apache Web server
  4.) Mysql
  
  All this are open source.. so no problem of purchasing or licensing.. I have already started and reading more about it from the drupal site and trying to learn myself.. so if you all are interested.. get this things and start creating your own websites...
  
  You can create your own forum like the Ms-forums on your own, maintain it too...
  

  Monday, May 21, 2007 3:48 PM
• 

  

  0

  Sign in to vote

  I already have php, mysql and apache installed in my machine, i am using that since 2-3 years.
  
  I have downloaded Drupal earlier, but i am feeling bored to try it out. Not of my interest much. hehe. But i am sure i will give it a try before my vacation finishes
  

  Monday, May 21, 2007 5:05 PM
• 

  

  0

  Sign in to vote

  Try installing wamp 5+ , it has php, mysql and apache all in one. Less configuration and easy installation.

  Tuesday, May 22, 2007 1:23 AM
• 

  

  0

  Sign in to vote

  Yes adnan i know about wamp. But i like to configure things on my own, and also i dont like much things loading at startup all the time Anyways i am used to the configuration since 2 years. No need for wamp. Wamp is for newbies.
  

  Tuesday, May 22, 2007 5:07 AM
• 

  

  0

  Sign in to vote

  oh..wamp....i have had experiences with wamp....i waned to use it as a php server.....actually wamp is really easy installation, you dont have to do much, it configures , most of the things for you, and it is recommended for beginners, you see, ....but its always good, if you like to work your way out at things, then you can give apche web server a try, it is very powerful and secure...i havent tried it though...

  Tuesday, May 22, 2007 1:10 PM
• 

  

  0

  Sign in to vote

  Yes adnan. Newbies should prefer wamp, as they dont need to go into much details about the configurations. But if you have about 3-4 months experience with php , apache etc, then i suggest you to install them seperately, as while you configure it you will get to know more abut what it offers, and about its actual power.
  

  Tuesday, May 22, 2007 2:24 PM
• 

  

  0

  Sign in to vote

  umm... i c...hey harshil, were u trying to write my name instead of adnan or what?....because i felt ur reply resembled a lot to my previous post ... as i was the one to mention in my prev post that it is meant for newbeis and stuff.....however adnan in his earlier posts did not mention this and was telling about how easy it is to use wamp....

  anyways, i must say, a good info is being being shared by u guys, regarding drupal and joomal, thanks to u varun and adnan,

  Wednesday, May 23, 2007 1:30 PM
• 

  

  0

  Sign in to vote

  @Anoop  - In my above post, i was trying to say both you and adnan sorry for not mentioning your name, i thought you would understand it, cause just above my post was yours
  

  Wednesday, May 23, 2007 3:45 PM
• 

  

  0

  Sign in to vote

  @harshil- common yaar how can i understand that , out of nowhere?..i aint an astrologer right...anyways no issues buddy..... ..enjoy...
  

  Thursday, May 24, 2007 10:59 AM
• 

  

  0

  Sign in to vote

  People, looks like we are deviating from the topic.. now i have already started studying drupal.. who all have started doing something like this???
  

  Thursday, May 24, 2007 11:14 AM
• 

  

  0

  Sign in to vote

  Well Drupal Seems to be quite interesting. Could you refer some books, that I could use to brush up on my PHP?
  

  Thursday, May 24, 2007 12:25 PM
• 

  

  0

  Sign in to vote

  sure maithille, i have got some ebooks, would you like to have any?
  

  Thursday, May 24, 2007 1:32 PM
• 

  

  0

  Sign in to vote

  @Anoop we would surely like to have some e-books on PHP, so please give us the link....
  
  @Maithille, though you dont require a knowledge of PHP for Drupal, but if you have it, its a bonus..
  You can learn Drupal from their help books available at www.drupal.org
  

  Thursday, May 24, 2007 2:01 PM