From Static To Dynamic

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

5 comments

Comments 1 - 5 of 5 previous next Post a comment

  • + gueste758c2 gueste758c2 5 months ago
    There are many ideas and methods very often
  • + MyTaskHelper MyTaskHelper 2 years ago
    Another way of adding dynamic to static site is using online database.

    See http://www.mytaskhelper.com - 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?
  • + MyTaskHelper MyTaskHelper 2 years ago
    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 http://www.mytaskhelper.com

    Is it have a sense?
  • + desertlibrarian desertlibrarian 3 years ago
    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.

  • + desertlibrarian desertlibrarian 3 years ago
    Presented at Internet Librarian 2007.

Post a comment
Embed Video
Edit your comment Cancel

Favorites, Groups & Events

From Static To Dynamic - 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. Initial Search Results
    • WebCMSs:
      • Lenya
      • Drupal
      • e107
      • eTouch
      • ExpressionEngine
      • Joomla!
      • Plone
      • WebGUI
      • Xoops
    • Wikis:
      • Giki
      • KeheiWiki
      • MediaWiki
      • MoniWiki
      • PHPwiki
      • PmWiki
      • PukiWiki
      • SnipSnap
      • TWiki
  10.  
  11. 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
  12. The Final Four
    • Drupal TWiki
    • WebGUI MediaWiki
    • These were installed and tested locally.
  13. Drupal: Adding Content
  14. WebGUI: Adding Content
  15. TWiki: Adding Content
  16. MediaWiki: Adding Content
  17. 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
  18. General Thoughts
    • Wanted familiar look-and-feel
    • Wanted terminology changed
    • Liked the CMSs
      • “ More like Word”
    • Disliked the wikis
      • “ Too much work”
  19. The Winner Is…
  20. Next Steps
    • Expanding functionality
    • Ingesting existing site
    • Training staff on use
    • Going live on new server by 2008
  21. Thanks for Listening! http://atst.nso.edu (after January 1 st ) Follow the rest of the journey at desertlibrarian.blogspot.com/search/label/cms

+ desertlibrariandesertlibrarian, 3 years ago

custom

1946 views, 0 favs, 2 embeds more stats

A brief overview of ATST's journey from static web more

More info about this document

© All Rights Reserved

Go to text version

  • Total Views 1946
    • 1853 on SlideShare
    • 93 from embeds
  • Comments 5
  • Favorites 0
  • Downloads 35
Most viewed embeds
  • 91 views on http://desertlibrarian.blogspot.com
  • 2 views on http://www.desertlibrarian.blogspot.com

more

All embeds
  • 91 views on http://desertlibrarian.blogspot.com
  • 2 views on http://www.desertlibrarian.blogspot.com

less

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

Cancel
File a copyright complaint
Having problems? Go to our helpdesk?

Categories