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.

From Static To Dynamic


Published on

A brief overview of ATST's journey from static web pages to a dynamic, Drupal-driven one.

Published in: Technology
  • Another way of adding dynamic to static site is using online database.

    See - free online database, where you can create forms and embed to your static site.

    Is it not another way of moving from static to dynamic?
    Are you sure you want to  Yes  No
    Your message goes here
  • I think online databases is an another good way for moving from static to dynamic.

    For example, if you have static site and want to create Mailing List. You can create mailing list database in online database, and embed with widget on your site.
    Se an example, free online database

    Is it have a sense?
    Are you sure you want to  Yes  No
    Your message goes here
  • This is a bad photo of my real-time evaluation system; it's a printout of results from CMSMatrix that I made notations on as time progressed.<br /><br/>
    Are you sure you want to  Yes  No
    Your message goes here
  • Presented at Internet Librarian 2007.<br /><br/>
    Are you sure you want to  Yes  No
    Your message goes here
  • Be the first to like this

From Static To Dynamic

  1. 1. From Static to Dynamic: Choosing and Implementing a CMS Ruth Kneale, National Solar Observatory, Advanced Technology Solar Telescope
  2. 2. What’s a CMS anyway? <ul><li>CMS = Content Management System </li></ul><ul><ul><li>Used to collaboratively and interactively create, manage, control, and publish information </li></ul></ul><ul><ul><li>Known by many other terms </li></ul></ul><ul><ul><ul><li>PDM or EDMS, like DocuShare </li></ul></ul></ul><ul><ul><ul><li>Web CMS, like Drupal </li></ul></ul></ul><ul><ul><ul><li>Wiki </li></ul></ul></ul><ul><ul><li>We need a web CMS </li></ul></ul>
  3. 3. Why do we want one? <ul><li>To avoid any more of the “single point syndrome” </li></ul><ul><li>To enable: </li></ul><ul><ul><li>Ease of administration </li></ul></ul><ul><ul><li>Increased team collaboration </li></ul></ul><ul><ul><li>Increased functionality </li></ul></ul><ul><ul><li>Improved presentation for the web site </li></ul></ul>
  4. 4. Our Basic Starting Point <ul><li>Open Source = $0 cost </li></ul><ul><li>LAMP Setup </li></ul>
  5. 5. Must Haves <ul><li>Audit trail </li></ul><ul><li>Content approval </li></ul><ul><li>WYSIWYG editor </li></ul><ul><li>Granular privileges </li></ul><ul><li>Friendly URLs </li></ul><ul><li>Versioning </li></ul><ul><li>Content reuse </li></ul><ul><li>CGI support </li></ul>
  6. 6. Should Haves <ul><li>Sandbox/staging area </li></ul><ul><li>Online administration </li></ul><ul><li>Inline administration </li></ul><ul><li>Mass uploading </li></ul><ul><li>Site map/index </li></ul>
  7. 7. Nice to Have <ul><li>Contact management </li></ul><ul><li>Drag-n-drop </li></ul><ul><li>Photo gallery </li></ul><ul><li>Events calendar </li></ul><ul><li>Web statistics </li></ul>
  8. 8. To CMS or to Wiki? <ul><li>That is the question </li></ul><ul><ul><li>Both are strong possibilities </li></ul></ul><ul><li>How to determine? </li></ul><ul><ul><li>Experience of others (listservs, etc) </li></ul></ul><ul><ul><li> and </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li> </li></ul></ul><ul><ul><li>Local evaluation </li></ul></ul>
  9. 9. Initial Search Results <ul><li>WebCMSs: </li></ul><ul><ul><li>Lenya </li></ul></ul><ul><ul><li>Drupal </li></ul></ul><ul><ul><li>e107 </li></ul></ul><ul><ul><li>eTouch </li></ul></ul><ul><ul><li>ExpressionEngine </li></ul></ul><ul><ul><li>Joomla! </li></ul></ul><ul><ul><li>Plone </li></ul></ul><ul><ul><li>WebGUI </li></ul></ul><ul><ul><li>Xoops </li></ul></ul><ul><li>Wikis: </li></ul><ul><ul><li>Giki </li></ul></ul><ul><ul><li>KeheiWiki </li></ul></ul><ul><ul><li>MediaWiki </li></ul></ul><ul><ul><li>MoniWiki </li></ul></ul><ul><ul><li>PHPwiki </li></ul></ul><ul><ul><li>PmWiki </li></ul></ul><ul><ul><li>PukiWiki </li></ul></ul><ul><ul><li>SnipSnap </li></ul></ul><ul><ul><li>TWiki </li></ul></ul>
  10. 11. The Weeding Begins <ul><li>Exclusions based on: </li></ul><ul><ul><li>Too many missing functionalities </li></ul></ul><ul><ul><li>Hidden fees </li></ul></ul><ul><ul><li>Currency of support </li></ul></ul><ul><ul><li>Required database underpinnings </li></ul></ul><ul><ul><li>Reports of others on ease of installation </li></ul></ul><ul><ul><li>Reports of others on ease of use </li></ul></ul><ul><ul><li>Short evaluation on opensourcecms </li></ul></ul>
  11. 12. The Final Four <ul><li>Drupal TWiki </li></ul><ul><li>WebGUI MediaWiki </li></ul><ul><li>These were installed and tested locally. </li></ul>
  12. 13. Drupal: Adding Content
  13. 14. WebGUI: Adding Content
  14. 15. TWiki: Adding Content
  15. 16. MediaWiki: Adding Content
  16. 17. Local Testing <ul><li>Small group of local users made up of staff who would also be final users of the product </li></ul><ul><li>Created, edited content </li></ul><ul><li>Provided feedback </li></ul>
  17. 18. General Thoughts <ul><li>Wanted familiar look-and-feel </li></ul><ul><li>Wanted terminology changed </li></ul><ul><li>Liked the CMSs </li></ul><ul><ul><li>“ More like Word” </li></ul></ul><ul><li>Disliked the wikis </li></ul><ul><ul><li>“ Too much work” </li></ul></ul>
  18. 19. The Winner Is…
  19. 20. Next Steps <ul><li>Expanding functionality </li></ul><ul><li>Ingesting existing site </li></ul><ul><li>Training staff on use </li></ul><ul><li>Going live on new server by 2008 </li></ul>
  20. 21. Thanks for Listening! (after January 1 st ) Follow the rest of the journey at