1 / 21

From Static to Dynamic:

From Static to Dynamic:. Choosing and Implementing a CMS. Ruth Kneale, rkneale@nso.edu National Solar Observatory, Advanced Technology Solar Telescope. What’s a CMS anyway?. CMS = Content Management System

yanni
Download Presentation

From Static to Dynamic:

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. From Static to Dynamic: Choosing and Implementing a CMS Ruth Kneale, rkneale@nso.edu National Solar Observatory, Advanced Technology Solar Telescope

  2. What’s a CMS anyway? • CMS = Content Management System • Used to collaboratively and interactively create, manage, control, and publish information • Known by many other terms • PDM or EDMS, like DocuShare • Web CMS, like Drupal • Wiki • We need a web CMS

  3. Why do we want one? • To avoid any more of the “single point syndrome” • To enable: • Ease of administration • Increased team collaboration • Increased functionality • Improved presentation for the web site

  4. Our Basic Starting Point • Open Source = $0 cost • LAMP Setup

  5. Must Haves • Audit trail • Content approval • WYSIWYG editor • Granular privileges • Friendly URLs • Versioning • Content reuse • CGI support

  6. Should Haves • Sandbox/staging area • Online administration • Inline administration • Mass uploading • Site map/index

  7. Nice to Have • Contact management • Drag-n-drop • Photo gallery • Events calendar • Web statistics

  8. To CMS or to Wiki? • That is the question • Both are strong possibilities • How to determine? • Experience of others (listservs, etc) • Cmsmatrix.org and wikimatrix.org • Opensourcecms.com • Experts-Exchange.com • Local evaluation

  9. WebCMS’s: Lenya Drupal e107 eTouch ExpressionEngine Joomla! Plone WebGUI Xoops Wiki’s: Giki KeheiWiki MediaWiki MoniWiki PHPwiki PmWiki PukiWiki SnipSnap TWiki Initial Search Results

  10. The Weeding Begins • Exclusions based on: • Too many missing functionalities • Hidden fees • Currency of support • Required database underpinnings • Reports of others on ease of installation • Reports of others on ease of use • Short evaluation on opensourcecms

  11. The Final Four Drupal TWiki WebGUI MediaWiki These were installed and tested locally.

  12. Drupal: Adding Content

  13. WebGUI: Adding Content

  14. TWiki: Adding Content

  15. MediaWiki: Adding Content

  16. Local Testing • Small group of local users made up of staff who would also be final users of the product • Created, edited content • Provided feedback

  17. General Thoughts • Wanted familiar look-and-feel • Wanted terminology changed • Liked the CMSs • “More like Word” • Disliked the wikis • “Too much work”

  18. The Winner Is…

  19. Next Steps • Expanding functionality • Ingesting existing site • Training staff on use • Going live on new server by 2008

  20. Thanks for Listening! http://atst.nso.edu (after January 1st)

More Related