25. • Project Goal: Centrally-hosted web development
platform for brochureware websites on campus.
• Centrally-maintained codebase
• Individually-maintained content and websites
• Minimize the technical requirements for creation
and maintenance of web development on campus.
PWP Basics
26. • Evaluated multisite offerings and existing services:
• Drupal Multisite
• Drupal OpenScholar
• WordPress Multisite (MU)
• Evaluated by three metrics:
• Ease-of-use
• Maintainability
• Feature sets
Phase 1: Fall 2014
33. • Kickstart development:
• Consult with GT IC about future Drupal themes,
trends, & additions.
• Bring GT Boilerplate close to GT Theme v2.5.
• Write initial documentation and best-practices.
• Bring on pilot users:
• Technical and non-technical faculty.
• Interested research groups and labs.
Phase 3: Spring 2015
34. • Commence Open Pilot:
• Begin communication and marketing (COCOA,
unit communicators, etc).
• Begin monthly open help-desk sessions.
• Initialize feedback and feature-request forms and
workflows.
Phase 4: Summer 2015
36. • Outreach and Expansion:
• Begin College/School Tour across campus.
• Continue open help-desks and marketing.
• Highlight ‘websites done right’.
• Expand the PWP Ownership group.
• Continue discussion on GT resources on PWP.
• Plan for future hardware, resource needs.
Phase 5: Fall 2015