Introduction of a CMS (Content Management System) in a HEP environment

[1] Welcome
* Web Office @ DESY since 2003
* Project of IT and PR
* Planning and staffing started 2002
* Manpower
  1 Concept / Programmer (CMS)
  1 Concept / Editorial Staff 
  1 Programmer (Building Sites)
  1 Technician (Hardware and System)
    {Was joined in later due to complexity of cluster-system}
  * Funding for Consulting (Technic and graphics)
    {Graphics was to be handled inhouse, which didn't prove practical}
  
[2] Grounds to start from
* Over 70 public accessable webservers
* Uncounted internal webservers with a variety of functionality
* Some single Websites with more the 2500 Pages
* No common design, neither in graphics nor in navigation
* Many Pages/Trees/Sites far from UpToDate
* No central support possible
  - HTML, WebObjects, Mini-CMS, EmbPerl, C/C++, Java ...
  - Solaris, Linux, Windows ...
  - Apache, IIS, ...

[3] Requirements from the Campus
* Mass hosting (license modell)
* Scalability (license modell)
* Multi Language
* Blueprints and packages for quick setup of new sites
* Quickly have real sites for testing
* Iterative development
* Interfaces to existing back-end systems
* Incorporation of existing (web-)functionality
* Design and core functions to be managed centrally

[4] Software chosen
* Python application server "Zope" http://www.zope.org/
* Content Management System "ZMS" http://www.zms-publishing.com/
* Completely Open Source
* Huge community world wide
* Many big installations of Zope up and running
* Professional consulting available
* Easy to extend
* Many special requirements already available as AddOns

[5] Building system, phase 1
* Single Machine (with failover)
* Sites built with common functionality
  - No central handling of these
  - Allowance for easy changes an extensions
* Design according to DESY-CI
  - No central handling for all sites
  - Allowance for easy tweaking due to functionality

* Learning a lot from groups and editorial staffs
* "Test"-websites swiftly used as productive systems
* Phase 1 was lasting almost two years

[6] Building system, part 2
* Clustersystem with 6+ Machines (being built atm)
* Design according to DESY-CI through central templates
* All extra functionality through central "Special Objects"
  - Users and groups from DESY-Registry
  - PlugIn of MS-Exchange calendars
  - Easy integration of web-functionality on campus
  - Access into and incorporation of files from AFS
  - Much more
* Giving back all developed code into Open Source
  
[7] Let's have a look
  http://zmsdemo.desy.de/
  
[8] Thanks for listening. Questions?
http://www.zope.org/
http://www.zms-publishing.com/
http://zmsdemo.desy.de/