Evaluating Open Source CMS Solutions
30 November -0001GOAL: To recommend appropriate technologies to the client.
At my company Mad Irish Group, LLC (MiG - http://www.madirishgroup.com) we are strong proponents of Open Source (OS) solutions. In addition to being free, OS solutions are supported by a wide developer community and extensive online documentation, help, and how-to's. Most OS CMS solutions are supported by Linux based hosting environments, which tend to be cheaper and easier to maintain remotely. OS solutions allow for complete transparency in any solution. Not only is source code made available for any customization or modification, but also the underlying technology is freely available. In addition to being cost effective, OS solutions ensure ongoing support is available and facilitate upgrades and migration. While proprietary solutions do exist, these lock the client into a permanent relationship with the proprietary vendor. At MiG we feel that proprietary solutions tend to lock your data into a format that is only supported by the vendor. With OS solutions you are never tied to a specific provider for updates, bug fixes, or additions. OS also allows the client to choose from a worldwide community for support. Because the source code is completely available to the client, they are in total control of their information and product. With OS the client retains total ownership of the product from the top down.
Discovery of Available CMS Options:
In order to accurately gauge the scope of available OS CMS's, popular OS CMS websites must be constantly monitored. The distributed nature of OS development means that new projects constantly evolve and forks of existing projects may present new options. As part of the OS Technology Group (OSTG - http://www.ostg.com/) Source Forge (http://www.SourceForge.net) is the most comprehensive site for OS projects. CMS Watch (http://www.cmswatch.com) is another good source for emerging and existing CMS's. Existing CMS options are also weighed against a custom built CMS created by developers specifically for the client. The OS nature of existing CMS's allows for modules and pieces of existing CMS's to be easily drawn into a custom CMS, so possible solutions could even include an amalgamation of existing and custom CMS solutions.
- Hidden costs associated with all CMS choices must be evaluated. If ongoing system upgrades or licenses will involve additional expense these factors should be noted before deploying a particular CMS.
- Are specialized hosting situations required for either the chosen CMS due to client needs?
- Are there any supplemental costs associated with the deployment, such as SSL certificates?
- Product Feature Set
- End product feature sets can be broadly defined as the feature set of the desired product. Will the product require blogs, member messaging, email to a friend features, RSS feeds, etc. CMS choices can be largely driven by the client feature requirements. Many CMS options offer various modules and core ingredients that may meet client needs out of the box. It is important to identify all desired features before evaluating any CMS. There may even be situation where the client needs are specific enough that a custom built CMS is warranted.
- Once all desired features have been identified each CMS can be evaluated based on its basic implementation, any additional modules, and the number and scope of custom modules can be weighed. This process is designed to determine which pre-built CMS will best fit the broadest scope of client needs with the least amount of customization. Once a best fit is established, it can be weighed against a custom built CMS.
- Custom-Built vs. Existing CMS
- Pre-existing CMS solutions are advantaged in that the essential Quality Assurance (QA) has already been done. A pre-existing CMS is assumed to have a strong code base that will function without bugs or problems, saving developer time for customization. Most pre-existing CMS solutions provide add-on modules that can be used to meet many client needs. OS CMS solutions can also easily be modified to meet customer specifications.
- Custom-built CMS's require more time to implement because outside of core components they must be built from the ground up. While this introduces a much longer QA and debugging cycle, a custom-built CMS can be structured to meet client needs specifically. While a pre-existing CMS may require major modification and revision, a custom-built CMS can be created on the fly to meet client demands.
- Support (in-house vs. contractor, initial vs. ongoing)
- Support should be a major consideration in choosing effective technologies. If the client already has in-house technical staff, their technical experience should be matched to the technology choice. If the client already employs in house technical staff that are knowledgeable in a certain technology, that should pre-dispose the technology choice to their area of expertise. If the client is looking to outside support, this should also be a consideration. In general it will be easier and cheaper to support OS solutions. OS functions on a principle of free community support which has created a large pool of inexpensive expertise. Closed source solutions will require more expensive support. CMS technology decisions should also be weighed against available support. Any CMS with an extensive user and support base will be more cost effective to maintain in the long run.
- Existing platforms
- The client's existing hardware and software architecture should also be taken into consideration when exploring CMS solutions. Often time's clients will have existing hosting environments that may dictate CMS choices. If the client has any preexisting licenses to software or hardware these should not be ignored when evaluating CMS options.
- Existing data
- Existing data that must be migrated into the CMS should also be evaluated. If existing data resides in a proprietary format then the cost of migration should be weighed against the use of similar proprietary format for the CMS.
- All existing and future data types must be noted. This includes any internal documents for publish or external sources (RSS, XML, etc.). The target CMS must be able to store, process, and manage these data types.
- Data Availability.
- Some organizations are mandated to make their data available in a known format to internal applications, business partners, clients or customers. These needs must be identified before choosing appropriate CMS solutions. If archival formats are required, these should also be noted. Many clients require a uniform data format for archiving or future upgrades. These considerations must be taken into account when evaluating CMS data storage (specifically database back end support).
- Content Process
- All content processing guidelines must be met by the target CMS. If content requires review, editing, or approval, each CMS must be evaluated in terms of its ability to meet these needs. Some CMS solutions support this workflow control better than others.
- Do one or more authors create the content? Are these authors centralized or distributed? These questions must be answered to determine which CMS will best support the client's content creation needs.
- Versioning and roll-back capabilities of each CMS must also be determined. If the client has extensive need for recall or versioning then the target CMS must be able to support this.
- Does the client have any URI requirements? Will content stay in static locations or will it move? If content location is variable the CMS must support URI to allow for dynamic linking of content.
- Administration needs
- Ease-of-use must be evaluated. Does the Administration of the CMS require extensive training? How available are help and other documents? Is the interface intuitive? The overall usability of the administration must be evaluated from an end user perspective.
- Are there any geographic considerations with the administration? Does the administration require an installation of software or is it enabled with third party software? How available is the administration (for instance to road warrior users)?
- Admin resources standardization should be considered. Does the administration interface appear uniformly on all platforms (and/or browsers). Does the administration interface require any third party software (such as a web browser) or is it a stand-alone application?
- New Data
- Does the CMS support new data types? If for an unforeseen reason the project must be expanded and new data types are added, the CMS must be able to conform to new data types with relative ease.
- Scalability & Scope
- The scalability of each CMS must be evaluated to determine if it will meet the client needs. In addition, the intended scope of each CMS must be noted. A CMS designed to run a large corporate site may not be the best choice for a small business with a limited number of pages. Some CMS'es can scale easily to meet client needs, but others may require such heavy modification to meet client scale and scope as to make them inappropriate.
- Is the client site built off of any sort of universal template or will there be multiple content formats that must be supported? Some CMS's support custom content presentation better than others.
- Does the intended CMS require reporting? If so the scope and scale of this reporting must be evaluated. Some clients will require only log file reporting, but others may need more detailed reporting statistics, including usage of specific functionality such as 'email to a friend' features.
- Does the target CMS support client needs such as SSL or user/group controls? The degree to which the target CMS supports client security needs is a major consideration. Encryption and user controls should both be evaluated. If the client has complex user architecture then this must be noted as well.
- Does the intended audience or administration require multi-lingual support? If so this must be taken into consideration when selecting a CMS. The administration interface as well as the presentation must be evaluated and support any client language needs.
- The standards compliance of each CMS must be evaluated. CMS's which support extensible, standards compliant formats will be valuable over the long term since they will allow for easier maintenance and migration of material. Each CMS should be evaluated in terms of its support of well-known and accepted standards such as XML (including XHTML), Dublin Core, CSS, etc.
- Is the CMS Section 508 compliant? How well does the CMS present information for persons with disabilities? Each CMS must be carefully examined to determine if it meets or exceeds standard usability guidelines.
- Membership and associated features
- Are there available member account features? What are the processes by which members sign-up? What features are available for member management (add/edit/delete)? Can any management be distributed among users and/or groups of administrators? Is member management scalable?