290 likes | 483 Views
Using Drupal at UCSF. UCSF ShareCase November 8, 2013 John Kealy, UCSF Senior Web Developer. Why Have a Website?. Publish Information Reach a Global Audience Update any time Promote Your Services Improve Customer Service Gather Information and Generate Leads.
E N D
Using Drupal at UCSF UCSF ShareCase November 8, 2013 John Kealy, UCSF Senior Web Developer
Why Have a Website? • Publish Information • Reach a Global Audience • Update any time • Promote Your Services • Improve Customer Service • Gather Information and Generate Leads
UCSF Website Statistics 3000 + websites at UCSF 400 + UCSF sites on Drupal $15k -$150k cost for building a single custom site
What is Drupal? • It’s Open Source Software • A Web Content Management System • www.whitehouse.gov • www.economist.com • www.theonion.com • Popular in education (26% of .edu sites) • It can be used to build websites and web applications
Why Should I Care? • Extensively used at UCSF • Main UCSF website • School of Medicine, Dentistry, etc. • Large Open Source Community • Thousands of “modules” • Thousands of developers • Very active community • Very flexible and extensible • Emerging as a UCSF standard
What’s the Catch? ITS is only providing hosting and Starter Kit for free. No site administration. No programming expertise provided. No design expertise provided. No site building provided Contractor or department expertise required
What Does Hosting Cover? Updating core website software Keeping Single Sign On available Monitoring the server Creating empty databases for new sites Managing access to server Managing access to code repository Migrating code, databases and files
What’s Not Covered by Hosting? Keep site specific software up to date Creating and managing site user accounts Creating content types and views Changing site layout Creating custom software or designs Content migration or entry … and a lot more…
Custom Sites: Pros Design tailored for site’s purpose Site tuned for specific needs
Custom Site: Cons Take significant time to create High cost to create Costly to maintain Difficult to support Difficult to train content editors
Costs: Large Custom Site • Examples: • www.ucsf.edu • Dentistry.ucsf.edu • Pharmacy.ucsf.edu • Build Cost: • 100 - 300K • Maintenance Costs: • Content 1-3+ FTE • IT Administration .25 - 1+ FTE
Costs: Medium Custom Site • Examples: • its.ucsf.edu • ptrehab.ucsf.edu • Qb3.org • Build Cost: • 50 - 150K • Maintenance Costs: • Content 1.5 + FTE • IT Administration .25+ FTE
Costs: Small Custom Site • Examples: • healthpolicy.ucsf.edu • stemcell.ucsf.edu • hub.ucsf.edu • Build Cost: • 10 - 60K • Maintenance Costs: • Content .25 + FTE • IT Administration .1+ FTE
Starter Kit Sites: Pros Fast to create Easy to maintain Low cost of ownership Features being added over time by ITS New features can be added by site owner
Starter Kit Sites: Cons Design not tailored for particular site Only basic functionalityto start with
How Do I Sign Up? Go to Help.ucsf.edu Select web services Select Drupal Web Hosting Request
UCSF Drupal Resources • The UCSF Drupal Community • UCSF Drupal Users Group (UCSF-DUG) • Monthly Users Helping Users (UHU) • Drupal.ucsf.edu • Drupal Chatter group and Listserv • ITS hosting • UCSF Drupal Customizations • MyAccess single sign on • Directory & Profiles integration • UCSF web editor
Drupal Community • Websites • Drupal.org (modules, forums, etc.) • www.lullabot.com (training videos) • Camps and conferences • Drupal Con June 2-6, 2015 Austin • Bay Area Drupal Camp (BADCamp) (fall)