BrainDump
  Home arrow BrainDump arrow Page 2 - Choosing an Open-Source Content Management System
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
VPS Hosting  
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid  
Request Media Kit
Contact Us  
Site Map  
Privacy Policy  
Support  
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
Google.com  
BRAINDUMP

Choosing an Open-Source Content Management System
By: Bruce Coker
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 12
    2008-12-15


    Table of Contents:
  • Choosing an Open-Source Content Management System
  • How to choose?
  • Which system?
  • More Systems

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article

     
     
    ADVERTISEMENT


    Choosing an Open-Source Content Management System - How to choose?
    ( Page 2 of 4 )



    Before discussing the merits of various specific systems, it's important to understand the various factors on which the choice of a CMS should be based. Some of these factors are technological while others are to do with business.

    Purpose

    The first consideration is the purpose which the CMS will be required to serve. This involves answering questions such as:

    • Will the CMS be required to serve an Intranet, the Internet, or both?
    • Will it replace an existing publishing system? This will have implications for the migration of existing data to the new system, and compatibility with pre-existing requirements.
    • What type of material will be published? This could include things like simple text pages, complex pages containing graphics and with particular layout requirements, dynamically generated content, and so forth.
    • What volume of data will the CMS be required to handle?

    When choosing the CMS, the information gained from this assessment can be matched against the capabilities and strengths of the various systems to ensure the winner will meet the requirements.

    Priorities

    Once the basic purpose has been determined, it is a good idea to prioritize the features that will be most valuable in the selected CMS. Make a list of required features and arrange them in order of greatest to least importance. The feature list will probably include things like:

    • Multi-author support: Does your system need to support and manage multiple authors by, for example, protecting documents from unauthorized change and allowing multiple ownership?

    • "Out of the box" capabilities: How necessary is it that the CMS does most or all of what you need without having to source or build additional modules?

    • Authoring tools: If your content is the heart of your CMS, then your authors are its heartbeat. It's worth ensuring that the CMS provides suitable tools that your authors will enjoy working with.

    • Metadata management: The CMS should provide adequate metadata management tools to ensure that your site meets your needs for searchability, multi-platform distribution, content re-usability, linking, and so forth.

    • Add-on modules: You may wish to add functionality to your site at a later date. The availability of appropriate modules will be critical to your ability to expand.

    • Ease of use: The maintenance and operation of the CMS must be within the technical capabilities of its users and support staff. There's no point in implementing a highly technical solution without having the knowledge required to work with it or keep it running.

    • Template structure and flexibility: The system's templates are the key to modifying the site's look and feel. Depending on your requirements in this area, you may want to pay particular attention to the templates, to ensure they allow you to make alterations easily and quickly and without too steep a learning curve.

    Technology

    A major consideration when choosing a CMS is the technology on which it is built and the third-party technologies on which it depends. This decision will have implications for the management, maintenance and support of the CMS itself, as well as the hardware and software environments within which it will run.

    Open-source content management systems are typically built on one or more of PHP, Java, Perl or XML, with by far the majority being PHP-based and a small minority using other technologies such as Perl and Python. Therefore the choice will be widest if PHP systems are considered, but the presence of infrastructure - whether hardware, software or human - that can better support one of the alternatives may be a significant factor in the final decision.

    Business

    Depending on the size and nature of the organization, various business aspects may need to be considered such as cost, training requirements, guarantees, support and maintenance arrangements, scalability and technical constraints.



     
     
    >>> More BrainDump Articles          >>> More By Bruce Coker
     

       

    BRAINDUMP ARTICLES

    - Replacing Oracle with PostgreSQL
    - Demystifying SELinux on Kernel 2.6
    - Yahoo and Microsoft Create Ad Partnership
    - The Advantages of Obscure Open Source Browse...
    - Dell Announces CSI-style Digital Forensics S...
    - Milepost GCC Speeds Open-Source Development
    - Learn These 10 Programming Languages
    - Tomcat Capacity Planning
    - Internal and External Performance Tuning wit...
    - Tomcat Benchmark Procedure
    - Benchmarking Tomcat Performance
    - Tomcat Performance Tuning
    - Wubi: Windows-based Ubuntu Installer
    - Configuring and Optimizing Your I/O Scheduler
    - Linux I/O Schedulers





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 5 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek