User:Ilya/OpenWetWare/CMS

• arguments for using a content management system:
  • there is some internal info that will not benefit from being world-writeable or even -readable

• What makes an enterprise wiki?

• OpenSourceCMS - demos
• The CMS Matrix - CMS comparisons
• CMS Comparison Table from ISCB page
• a list of CMS

• How does Drupal compare to Plone?

• Drupal
  • Features
  • PHP, MySQL, Apache
  • easy install
  • good for communities and hobbyst projects
  • simple and clear internal structure, which requres minimum time for learning to use and administer it
  • example site: Pharmer.org
  • "all content is available as soon as it's written" model
  • Using open source software to design, develop, and deploy a collaborative Web site - Drupal, MySQL, PHP, Apache, Eclipse, CVS

• Plone
  • Python, Zope (may use Apache)
  • industrial, heavy-duty CMS
  • good for large corporate and intranet sites
  • more powerfull permissions system
  • Boston Plone Users Group

• PLoS ONE uses TOPAZ application framework
• TYPO3
• Mambo Server
• MamboForge
• Apache Lenya- Java/XML
• Textpattern
• Magnolia
• Metadot - portal server and intranet
• phpWebSite
• Joomla!
• alahup! is both a framework that lets web designers develop full featured, professional, standards compliant dynamic web sites, and an integrated content management system (features "semantic editing" though a customized Flash interface).
• Radiant CMS is a no-fluff, open source content management system designed for small teams (built with Ruby on Rails)