1. Content Management Systems 2010 Drew Loika

2. What is a CMS?  Allows a large number of people to contribute  Controls access  Provides easy storage and retrieval of data  Reduces repetitive actions  Improves communication  Don’t reinvent the wheel!

3. CMS Types  CMS – Content Management System  ECM – Enterprise Content Management  WCMS – Web Content Management System  Document Management  Media Content Management  Learning Content Management

4. Business Models  Open source  Open source with commercial modules  Open source with commercial support/consulting  Open source with commercial extensions  Closed source

5. ECS CMS  Main site  Purpose  Marketing, Research Material, Updates  Content  Text, PDF, PowerPoint  Research material  Presentation  Search  Manage  Categorize/Organize  Project sites  TBD  Forum, Photo Gallery, File Downloads, Calendar, Surveys, Mail Form, Wiki, Newsletter

6. ECS CMS  Easy  User driven  No IT  Start Small  Many Sites  Showcase  Archive old content

7. How to Choose  Core (Content Management)  Editor  Managing Assets/Artifacts  Search  Customization  User Interaction  Support  Roles & Permissions  Presentation  Versioning  Multiples Sites  SEO  Analytics  Technical Quality  Community  Other

8. Core (Content Management)  Workflow  Scheduling  Content Type  Media  Photo, video  Textual  Blog, forum, FAQ, wiki, newsletter  Calendar/Schedule  Other  Shopping, web links  Sandbox

9. Editor (WYSIWYG)  Inline  Control/admin panel  Media  Photo crop & rotate  Spell check

10. Managing Assets/Artifacts  Uploading  Organizing  Categorize, Tag, Search  Display  Update  Remove  WebDAV  Common Internet File System (CIFS)

11. Search  Site  Site content  File types

12. Customization  Easily extendable to meet future business needs?  Technology platform  Licensing  Customization/extension support

13. User/Consumer Interactions  Comment  Rating  Poll  Survey  Quiz  Form  Chat  Forum

14. Roles & Permissions  Interface trimming  Granularity

15. Presentation  Browser  Mobile  Print  Syndication

16. Versioning  Rapid recovery from mistakes  Greater security priviledges

17. Multiple Site Support  Leverage existing infrastructure & design  Different design  External collaborators

18. Multilingual Support  Supported?  Supporting meaningfully?  Interface  Manage changes & synchronization of translated versions?

19. SEO  Friendly URI’s  Better page rank

20. Analytics  Google Analytics

21. Technical Quality  How well does it function?  What does the code look like under the hood?

22. Community  May be primary source of support  Large enough?  Friendly?  Answer newbie and expert questions alike?

23. Support  Availability?  Geographic availability?  Relative cost?  Sophistication?

24. Other  AJAX  Country of origin  Active Directory  Technology stack  Database  Commercial implementation  Commercial training  Commercial manuals

25. Hidden Costs  Costs of Training  Cost of Quality  Cost of Functionality  Redundancy & Flexibility  Cost of Commitment  Content Management Interoperability Services (CMIS)

26. How to Implement  Risk Management  Establish Requirements  Identify Candidate CMS  Trial Candidates w/ Key Staff  Identify & Implement Organization, Practices  Deploy CMS  Training  Migrate Content  Identify Areas for Future Improvement

27. Risk Management  Constrain scope  Pilot project  Incorporate feedback

28. Establish Requirements  Clearly define outcomes & goals  Focus on business needs, NOT on technical  Address compliance needs  Record keeping, accessibility, legal risk, security risk  Identify users  Predict usage pattern  Predict information quality  Predict satisfaction

29. Identify Candidate CMS  Use established criteria to identify likely candidate CMS  Test against established criteria to narrow CMS pool  Use non-essential criteria to prioritize CMS pool (technology stack)  Consider total cost of ownership

30. Trial Candidates  Trial with multiple types of users  Use scenarios that match requirements (script)  Consider total cost of ownership

31. Organization & Practice  What goes where?  Who’s responsible for approving content?  Who’s responsible for enforcing content policy?  How will ongoing training occur? How will new employee training occur?  How will consistency be implemented & enforced?  Who gets a sub-site?  What ISN’T supported?

32. Deploy CMS  Depends on the CMS

33. Training  Type  Written  Video  In-person  Up-to-date material  Different user targets  Incorporate established policy?

34. Migrate Content  Good training tool

35. Future Improvements  Current guesses  Integration w/ ECS applications  Integration w/ ECS reports  Unknown?

36. Selection Process

37. Favorite Systems  Concrete5  dotCMS  eZ Publish  Kooboo  MODx  mojoPortal  SilverStripe  Sitefinity

38. Concrete5  PHP stack, open- source, supported  Commercial modules  Intended for consultants to build sites for clients  MVC  Hosting available

39. dotCMS  Java, open- source, supported, enterprise  For-pay enterprise version  Used for large, popular sites

40. eZ Publish  PHP stack, open-source, supported, commercial, enterprise, award winner  Norwegian

41. Kooboo .NET, open- source, very small, very new, Chinese  ASP.NET MVC

42. MODx  PHP stack, open-source, supported, award winner, AJAXy, smaller, newer

43. .NET, open-source, cloud  Technical focus (Trimmable?) mojoPortal

44. SilverStripe  PHP stack, open- source, supported, lightweight, award winner

45. Sitefinity .NET, Telerik, closed-source, commercial ($900)  Web forms, master pages, MVVM  Commercial & free modules

46. Notable Mentions  DotNetNuke – Most popular.NET CMS  Drupal – Open-source CMS w/ most mindshare  Joomla! – Extremely popular open-source CMS for small projects  Plone – Enterprise grade open-source CMS  Sharepoint 2010 – No introduction needed