PH/SFT web content experiences

Stefan RoiserPH/SFT

Entice 2

SFT web content types

• Static– Plain HTML – authored via Frontpage / Dreamweaver – Twiki – using the CERN service– Automatically generated – afs based, eg. Doxygen

• Dynamic– Mysql / Python – release info, nightly builds overview– J2EE source code X referencing – via CERN service

• SFT Services– Savannah– Hypernews

9 June 2010

Entice 3

Problems

• Incoherent look and feel• Difficult to maintain

– E.g. Frontpage generated HTML• Different URLs for content types• Investigation of Sharepoint

– At some stage only editable via IE– Also missing functionality in other browsers– Sharepoint wiki syntax differs

9 June 2010

Entice 4

Drupal

• Easy web based way to provide content via– WYSIWIG editor, pure html, PHP,– Any browser works

• Grouping in blogs, pages, books, wikis• A LOT of extra modules available

– authentication, security, taxonomy, mobile, …• Many different themes for page personalizing • Currently a setup of Drupal in SFT exists

– Instances for the group, projects, work packages

9 June 2010

Entice 5

monthly

Infrastructure

Hosted by

afs(daily)

9 June 2010

Backup

IT Services

Entice 6

SFT Pages

9 June 2010