Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How To Implement a CMS

7,768 views

Published on

Presented to the Long Island Library Resources Council on August 16, 2010.

  • Be the first to comment

How To Implement a CMS

  1. 1. Implementing a Content Management System Jonathan M. Smith [email_address] The Catholic University of America Long Island Library Resources Council August 16, 2010
  2. 2. By the end of this session you will... <ul><ul><li>Be familiar with the current landscape of CMS solutions </li></ul></ul><ul><ul><li>Have an understanding of CMS administration </li></ul></ul><ul><ul><li>Have a process for implementing a CMS </li></ul></ul><ul><ul><li>Be familiar with common technical requirements of CMS </li></ul></ul><ul><ul><li>Have an understanding of design and evaluation methods </li></ul></ul><ul><li>This session will describe the entire process of implementing a CMS; from requirements gathering to post-launch evaluation. </li></ul>
  3. 3. Systems Development Life Cycle
  4. 4. Survey Image credit:  http://www.flickr.com/photos/wessexarchaeology/321370565/in/pool-84525923@N00/
  5. 5. Platforms used by CUA Libraries <ul><ul><li>Mambo (open source) </li></ul></ul><ul><ul><ul><li>intranet (2005-06) </li></ul></ul></ul><ul><ul><li>Joomla! (open source) </li></ul></ul><ul><ul><ul><li>intranet (2006-present) </li></ul></ul></ul><ul><ul><li>Wordpress (open source) </li></ul></ul><ul><ul><ul><li>blog </li></ul></ul></ul><ul><ul><li>LibGuides (proprietary) </li></ul></ul><ul><ul><ul><li>research guides </li></ul></ul></ul><ul><ul><li>Topaz (in-house developed CMS) </li></ul></ul><ul><ul><ul><li>public site </li></ul></ul></ul>
  6. 6. Planning Image Credit:  http://www.flickr.com/photos/justindc/819823101/
  7. 7. Why use a CMS? <ul><ul><li>Distributed content creation </li></ul></ul><ul><ul><li>Separation of content and presentation </li></ul></ul><ul><ul><li>Integration with Web 2.0 tools </li></ul></ul><ul><ul><ul><li>forums, RSS, comments, videos, calendars </li></ul></ul></ul><ul><ul><li>Web based administration </li></ul></ul><ul><ul><ul><li>limits need for VPN, FTP, SSH  </li></ul></ul></ul>
  8. 8. Project document <ul><ul><li>Begin with a mission statement </li></ul></ul><ul><ul><li>Mission objectives </li></ul></ul><ul><ul><li>Cost estimate </li></ul></ul><ul><ul><li>Anticipated timeline </li></ul></ul><ul><li>Tips </li></ul><ul><ul><li>Document everything! </li></ul></ul><ul><ul><li>Involve stakeholders </li></ul></ul><ul><li>Just Enough Project Management by Curtis Cook </li></ul>
  9. 9. Analysis Image credit:  http://www.flickr.com/photos/gsfc/4662884851/
  10. 10. Establishing needs <ul><ul><li>Desired functionality </li></ul></ul><ul><ul><li>User management </li></ul></ul><ul><ul><li>Content ownership </li></ul></ul><ul><ul><li>Accessibility </li></ul></ul><ul><ul><li>Customization </li></ul></ul><ul><ul><li>Standards compliance </li></ul></ul><ul><ul><li>Existing content </li></ul></ul><ul><ul><li>? </li></ul></ul>
  11. 11. Get feedback from staff and patrons Image credit:  http://www.flickr.com/photos/iain/2548951967/
  12. 12. Hosting options <ul><ul><li>Local </li></ul></ul><ul><ul><ul><li>most flexible </li></ul></ul></ul><ul><ul><ul><li>need local expertise </li></ul></ul></ul><ul><ul><li>Organization (city, university) </li></ul></ul><ul><ul><ul><li>possible limitations? </li></ul></ul></ul><ul><ul><ul><li>level of support </li></ul></ul></ul><ul><ul><li>Commercial </li></ul></ul><ul><ul><ul><li>$$$$ </li></ul></ul></ul><ul><ul><ul><li>experience with CMS </li></ul></ul></ul><ul><ul><ul><li>similar customers? </li></ul></ul></ul>
  13. 13. Server requirements <ul><li>Operating system </li></ul><ul><ul><li>Linux, Windows, OS X </li></ul></ul><ul><li>Server platform </li></ul><ul><ul><li>Apaches, IIS ( Internet Information Services) </li></ul></ul><ul><li>Languages </li></ul><ul><ul><li>PHP, Perl, Java, Python, VB, etc. </li></ul></ul><ul><li>Databases </li></ul><ul><ul><li>MySQL, Oracle, SQL Server, PostgreSQL, etc. </li></ul></ul>
  14. 14. Software stacks <ul><li>LAMP - Common open source platform: </li></ul><ul><ul><li>Linux (os) </li></ul></ul><ul><ul><li>Apache (web server) </li></ul></ul><ul><ul><li>MySQL (dbms) </li></ul></ul><ul><ul><li>PHP (scripting language) </li></ul></ul><ul><li>WINS </li></ul><ul><ul><li>Windows Server (os) </li></ul></ul><ul><ul><li>IIS (web server) </li></ul></ul><ul><ul><li>.NET (programming language) </li></ul></ul><ul><ul><li>SQL Server (dbms) </li></ul></ul>
  15. 15. License  <ul><ul><li>Proprietary </li></ul></ul><ul><ul><ul><li>Requires least expertise </li></ul></ul></ul><ul><ul><ul><li>Cost $$$$ </li></ul></ul></ul><ul><ul><ul><li>http://www.cmswatch.com/ </li></ul></ul></ul><ul><ul><li>Open Source </li></ul></ul><ul><ul><ul><li>Requires some expertise </li></ul></ul></ul><ul><ul><ul><li>Potential for $ savings </li></ul></ul></ul><ul><ul><li>In-house </li></ul></ul><ul><ul><ul><li>Requires most expertise </li></ul></ul></ul><ul><ul><ul><li>Most custom </li></ul></ul></ul>
  16. 16. Evaluation of potential solutions <ul><ul><li>Version number </li></ul></ul><ul><ul><li>Year introduced  </li></ul></ul><ul><ul><li>Price </li></ul></ul><ul><ul><li>Stability, ongoing development </li></ul></ul><ul><ul><li> Active user community (critical for open source) </li></ul></ul><ul><ul><li>Documentation </li></ul></ul><ul><ul><li>Create a requirements comparison document </li></ul></ul><ul><ul><li>Assign a weight to each requirement </li></ul></ul>
  17. 17. Feature list <ul><li>CMS Matrix  http://www.cmsmatrix.org/ </li></ul><ul><ul><li>Migration tools </li></ul></ul><ul><ul><li>Incoming and outgoing RSS feeds </li></ul></ul><ul><ul><li>WYSIWYG text editors </li></ul></ul><ul><ul><li>Spell checker </li></ul></ul><ul><ul><li>Display media (flash, audio, video, etc.) </li></ul></ul><ul><ul><li>Template editor </li></ul></ul><ul><ul><li>Workflow - review and publish, messaging, status </li></ul></ul><ul><ul><li>Versioning </li></ul></ul><ul><ul><li>Reporting - clicks, searches, performance </li></ul></ul><ul><ul><li>Built-in backup </li></ul></ul><ul><ul><li>Security </li></ul></ul><ul><ul><li>Mobile access </li></ul></ul><ul><ul><li>Taxonomy </li></ul></ul>
  18. 18. Use the right tool <ul><li>Alternatives to a full fledged CMS: </li></ul><ul><ul><li>Wordpress (blogging platform, CMS lite) </li></ul></ul><ul><ul><ul><li>http://wordpress.org/ </li></ul></ul></ul><ul><ul><li>LibGuides, CommunityGuides (proprietary, hosted) </li></ul></ul><ul><ul><ul><li>  http://springshare.com/ </li></ul></ul></ul><ul><ul><li>Omeka (digital collections, exhibits) </li></ul></ul><ul><ul><ul><li>http://omeka.org/ </li></ul></ul></ul>
  19. 19. Open source CMS <ul><li>Resources </li></ul><ul><ul><li>Demos -  http://php.opensourcecms.com/ </li></ul></ul><ul><ul><li>CMS Design Resource -  http://www.cmsdesignresource.com/ </li></ul></ul><ul><ul><li>CMS Critic -  http://www.cmscritic.com/ </li></ul></ul><ul><ul><li>LibSuccess Wiki -  http://www.libsuccess.org/index.php?title=Content_Management_Systems_(CMS) </li></ul></ul>
  20. 20. Open source CMS focus <ul><ul><li>Wordpress </li></ul></ul><ul><ul><li>Joomla! </li></ul></ul><ul><ul><li>Drupal </li></ul></ul><ul><ul><li>Plone </li></ul></ul><ul><li>Other popular CMS </li></ul><ul><ul><li>MODx  http://modxcms.com/ </li></ul></ul><ul><ul><li>Typo3  http://typo3.com/ </li></ul></ul><ul><ul><li>Xoops  http://www.xoops.org </li></ul></ul><ul><ul><li>Squarespace   http://www.squarespace.com </li></ul></ul><ul><ul><li>DotNetNuke  http://www.dotnetnuke.com/ </li></ul></ul>
  21. 21. Wordpress <ul><li>http://wordpress.org/ </li></ul><ul><li>Current version:  3.0.1 </li></ul><ul><li>Min. server requirements: </li></ul><ul><ul><li>Apache </li></ul></ul><ul><ul><li>MySQL 4.1.2 </li></ul></ul><ul><ul><li>PHP 4.3 </li></ul></ul><ul><li>Version 3.2 will require MySQL 5.0.15+ and PHP 5.2+ </li></ul><ul><ul><li>Planned release first half of 2011 </li></ul></ul>
  22. 27. Joomla! <ul><li>http://www.joomla.org/ http://www.joomlainlibrary.com/ </li></ul><ul><li>Current Version: 1.5.20 </li></ul><ul><li>Min. server requirements: </li></ul><ul><ul><li>Apache 1.3 or IIS 6 </li></ul></ul><ul><ul><li>MySQL 3.23 </li></ul></ul><ul><ul><li>PHP 4.3.10 </li></ul></ul><ul><li>Version 1.6 will require MySQL 5.0.4+  and PHP 5.2+ </li></ul><ul><ul><li>Planned release late summer 2010 </li></ul></ul>
  23. 33. Drupal <ul><li>http://drupal.org/ http://drupalib.interoperating.info/ </li></ul><ul><li>Current version:  6.19 </li></ul><ul><li>Min. server requirements: </li></ul><ul><ul><li>Apache 1.3 or IIS 5 </li></ul></ul><ul><ul><li>MySQL 4.1 or PostgreSQL 7.1 </li></ul></ul><ul><ul><li>PHP 4.4 </li></ul></ul><ul><li>Version 7 will require MySQL 5.0.15 or PostgreSQL 8.3, and PHP 5.2 </li></ul><ul><ul><li>Planned release fall 2010 </li></ul></ul>
  24. 39. Plone <ul><li>http://plone.org/ http://www.plone4lib.org/ </li></ul><ul><li>Current version: 3.3.5 </li></ul><ul><li>Min. server requirements: </li></ul><ul><ul><li>Apache </li></ul></ul><ul><ul><li>Python and Zope </li></ul></ul><ul><ul><li>MySQL, PostgreSQL, SQLite, or Oracle </li></ul></ul><ul><li>Version 4 </li></ul><ul><ul><li>Planned release summer 2010 </li></ul></ul>
  25. 43. Learning and support <ul><ul><li>Books, articles </li></ul></ul><ul><ul><li>Documentation </li></ul></ul><ul><ul><li>User group meetings </li></ul></ul><ul><ul><li>Hire a consultant </li></ul></ul><ul><ul><li>Install test site as a sandbox </li></ul></ul>
  26. 44. Design Image credit: Dan Skrobak  http://www.flickr.com/photos/daniel-skrobak/2258608480/
  27. 45. User centered design <ul><ul><li>Card sorting exercise </li></ul></ul><ul><ul><li>Google Analytics </li></ul></ul>
  28. 46. Taxonomy <ul><ul><li>Navigation doesn't need to reflect file structure </li></ul></ul><ul><ul><li>For intranet, function over department </li></ul></ul><ul><ul><li>For public site, a secondary taxonomy based on user group </li></ul></ul>
  29. 47. Visual design <ul><ul><li>Sketch </li></ul></ul><ul><ul><li>Photoshop mock-up </li></ul></ul><ul><ul><li>Working example </li></ul></ul><ul><li>Templates, themes   </li></ul>
  30. 48. Content <ul><ul><li>Use existing content </li></ul></ul><ul><ul><ul><li>How will it be transferred? </li></ul></ul></ul><ul><ul><li>Develop new content </li></ul></ul><ul><ul><ul><li>Who will write the content? </li></ul></ul></ul>
  31. 49. Enforcing security <ul><ul><li>Use robot.txt to block indexing by search engines </li></ul></ul><ul><ul><ul><li>  http://www.robotstxt.org/ </li></ul></ul></ul><ul><ul><ul><li>  Google Webmaster Tools:  http://is.gd/ehyEU </li></ul></ul></ul><ul><ul><li>Use noindex meta tag to block individual pages </li></ul></ul><ul><ul><ul><li>  Google Webmaster Tools:  http://is.gd/ehyHS </li></ul></ul></ul><ul><ul><li>CMS may have built in controls for public/private content </li></ul></ul>
  32. 50. Implementation Image credit: Jake Brewer  http://www.flickr.com/photos/integralfocus/83966554/
  33. 51. Server setup <ul><ul><li>Development server </li></ul></ul><ul><ul><ul><li>For testing new features, upgrades </li></ul></ul></ul><ul><ul><li>Production server </li></ul></ul><ul><ul><ul><li>Live server </li></ul></ul></ul><ul><ul><li>Backup server </li></ul></ul><ul><ul><ul><li>Backup procedures for site and database </li></ul></ul></ul><ul><ul><ul><li>Keep relevant server configurations in sync </li></ul></ul></ul>
  34. 52. Deployment <ul><ul><li>Install the CMS </li></ul></ul><ul><ul><li>Configure to your specifications </li></ul></ul><ul><ul><li>Apply the visual design </li></ul></ul>
  35. 53. Content migration <ul><ul><li>Intranet </li></ul></ul><ul><ul><ul><li> Manually transferred the existing content </li></ul></ul></ul><ul><ul><ul><li>A lot of new content was planned </li></ul></ul></ul><ul><ul><li>Public site </li></ul></ul><ul><ul><ul><li>1,400+ html pages </li></ul></ul></ul><ul><ul><ul><li>Univ. IT wrote scripts to import content </li></ul></ul></ul><ul><ul><ul><li>To 3 people a couple of weeks to clean up  </li></ul></ul></ul><ul><ul><li>Many CMS have plugins to aid migration from DB </li></ul></ul>
  36. 54. User testing Image credit: Terri Miller  http://www.flickr.com/photos/terriem/59397745/
  37. 55. Training Image credit:  http://www.flickr.com/photos/mjzitek/475244661/
  38. 56. Launch! Image credit: Chris Christner  http://www.flickr.com/photos/toptechwriter/364206324/
  39. 57. Maintenance Image credit: Emir Jones  http://www.flickr.com/photos/47557199@N03/4493925470/
  40. 58. Thank you! <ul><li>Jonathan M. Smith </li></ul><ul><li>twitter.com/l1br4r14n </li></ul><ul><li>[email_address] </li></ul><ul><li>Slides available at:   http://faculty.cua.edu/smithjm/lilrc-cms.html </li></ul>

×