60 likes | 172 Vues
Explore the evolution of web content management within SFT, transitioning from outdated systems like Frontpage and SharePoint to the robust capabilities of Drupal. Discover the advantages of using a WYSIWYG editor, support for multiple content formats, and the ability to personalize pages with various themes. This shift addresses issues such as incoherent design and maintenance challenges, while also providing enhanced functionalities like authentication, security, and mobile responsiveness. The current setup of Drupal for the SFT group showcases its potential to improve content organization and user experience.
E N D
PH/SFT web content experiences Stefan Roiser PH/SFT
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 Entice
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 Entice
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 Entice
Infrastructure monthly afs (daily) Backup IT Services Hosted by Entice
SFT Pages Entice