Last month we sponsored, “
Open Source CMS: Panacea or Pandora’s Box?
” along with
Acquia
and
Aquent
. Rob Klause, senior practice manager at Siteworx, and CMS analyst
Tony Byrne
offered key best practices for and challenges to selecting and deploying an open source CMS. 

With over 20 years of combined expertise, the two open source heavyweights discussed how to best integrate or use the various products and platforms available in the open source arena. Specifically, as a former White House insider, Rob proposed reasons why open source emerged as the best solution for Whitehouse.gov, which was built on the Drupal Web content management (WCM) platform. Tony similarly commented on the vendor landscape and how to best connect the right content management solution with user and technology needs. 

The two-hour discussion resulted in several key takeaways. For example:

1. When it comes to choosing an open source solution
avoid the RFP
checklist and evaluate how the solution fits your usability needs.  

• Ask yourself: “
  How does this open source platform or product fit user experience needs
  and what does it do best?”
• Throw out the RFP list and
  save time by developing a narrative of the use cases that exist within your organization
  .  Then, further reduce your choices based on how the product or platform addresses those specific use cases.  When the decision comes down to two alternatives, run a test case on both and pick the solution that performs best.  
• The best open source solutions offer agility and innovation along with access to a vibrant and well-supported community
  .  A solution without such components can limit scalability and extensibility. 
• If internal resources
  to routinely maintain and upgrade the system and install security patches (etc.)
  are limited, resist purchasing a complex open source platform
  —which may include a confusing array of add on modules.
• For large enterprises wishing to use open source,
  it’s ok to select a core commercial product and integrate open source solutions to deliver a custom fit platform
  ; just be sure that both solutions are scalable and compatible with future added solutions.

2. Just because its “open” source doesn’t
mean it’s free!

• Development, configuration, and coding all require a significant amount of manpower
  …not to mention testing and implementation.  
• The cost of securing your platform can add up.  Be sure to “trust but verify” the open source solution
  ; whether the platform or product is based on open source or is proprietary, assess the level of security your website needs and scope out what it will take (man hours and added security solutions) to maintain that level.
• Security doesn’t end with securing the CMS software, it’s also about securing the entire system
  ; i.e., the servers, the network, etc. and having a comprehensive security plan; i.e., the who, what, when, why and how of proactive and reactive planning for security incidents or events.
• Lean on good advice.
    Who better to give advice on a specific open source platform/product than those already using it?  Before you launch your own open source CMS, check-in with fellow users and learn how they are benefiting.

A full audio and visual recording is now available for you to
download
.