Supporting Drupal-as-a-Service Providing Tech Support to Drupal Devs - - PowerPoint PPT Presentation

supporting drupal as a service
SMART_READER_LITE
LIVE PREVIEW

Supporting Drupal-as-a-Service Providing Tech Support to Drupal Devs - - PowerPoint PPT Presentation

Supporting Drupal-as-a-Service Providing Tech Support to Drupal Devs Add speaker name here Kyle Hakala University of Minnesota Add speaker name here Drupal Lite Drupal Enterprise Who are our customers? Professors (well, graduate


slide-1
SLIDE 1
slide-2
SLIDE 2

Add speaker name here

Providing Tech Support to Drupal Devs

Supporting Drupal-as-a-Service

Kyle Hakala

University of Minnesota

slide-3
SLIDE 3

Add speaker name here

slide-4
SLIDE 4

Drupal Lite Drupal Enterprise

slide-5
SLIDE 5

Add speaker name here

  • Professors (well, graduate students…)
  • External contractors
  • Student Groups
  • Staff
  • a. Executive Assistants
  • b. Designers
  • c. Lab staff
  • d. IT folks — developers, sysadmins, etc.
  • e. “The IT people”
  • f. “The IT person”
  • g. “Our student worker this summer”
  • h. → etc…

Who are our “customers?”

slide-6
SLIDE 6

Add speaker name here

Lifecycle of a Site

☏ Requesting ✎ Developing ⎈ Launching ☯ Maintaining ♹ Retiring

From a Process Perspective

slide-7
SLIDE 7

Add speaker name here

Mentality: “We provide the canvas on which you paint” What do we need?

  • 1. domain name
  • 2. owner
  • 3. platform choice — Lite vs Enterprise
  • 4. (sometimes: approval)

☏ Requesting a New Site

Lifecycle of a Site

slide-8
SLIDE 8

Add speaker name here

Mentality: “Here are all the tools you need” What do we do on top of that?

  • 1. train/guide site owners
  • 2. provide light consultation
  • 3. troubleshoot issues (it’s always caches…)

✎ Developing a Site

Lifecycle of a Site

slide-9
SLIDE 9

Add speaker name here

Mentality: “Here, have some gatorade and a flu-shot” How do we help?

  • 1. maintain security
  • a. core updates
  • b. module updates
  • c. security certificates
  • 2. troubleshoot caches…
  • 3. run-of-the-mill Q&A

☯ Maintaining a Site

Lifecycle of a Site

slide-10
SLIDE 10

Add speaker name here

Mentality: “It’s a been a good run — here’s a backup!” What do we need?

  • 1. approval
  • 2. more approval
  • 3. final approval

☣ Retiring a Site

Lifecycle of a Site

slide-11
SLIDE 11

Add speaker name here

  • Self Help Guides:

○ Creating sites (content types, views, etc) ○ Content planning strategy ○ Contributing content ○ Administering/managing a site ○ GitHub guides

  • Standalone knowledge articles

○ Setting up a local dev environment ○ Configuring search & analytics

  • Walk-in Support Labs

What resources do we provide?

  • Email lists/groups
  • External resources:

○ branding ○ accessibility ○ training with Lynda.com ○ approved consultants list

  • Links to other live websites across UMN
  • Phone, email, chat support (business hours)
slide-12
SLIDE 12

Yes, and it’s part of the service!

Red tape everywhere!

  • No server access

○ No Drush commands ○ No fileserver or database access ○ No production code deployments

  • Administrator role is only for

Enterprise site owners.

  • Drupal Lite sites get pared-down admin access.

■ Can’t enable modules ■ Theme is non-negotiable

  • Branding is required
  • We’re here to keep the lights on (and safe!)

○ We’ll make sure your site is configured well ○ We back up your database and files ○ We’re here to help you launch your site

  • We’re here to support Administrators

if things break for them too

  • Drupal Lite gives you the access you need

■ We’ll help enable modules ■ We provide the theme

  • You can choose the

color scheme!

slide-13
SLIDE 13

Add speaker name here

Surely you don’t let people deploy custom code...

–A rightfully skeptical skeptic

“ “

slide-14
SLIDE 14

Add speaker name here

What is allowed in “Custom Code”

Organized chaos.

slide-15
SLIDE 15

Add speaker name here

The Past

See: both sides of the Grand Canyon

slide-16
SLIDE 16

Add speaker name here

Continuum Want Enterprise? Want Lite? Cheap plug: Folwell Design System presentation 3:15–4:00 — Room 244

The Future™

Also organized chaos.

slide-17
SLIDE 17

Add speaker name here

What if you don’t know the answer to someone’s question?

“ “

slide-18
SLIDE 18

Add speaker name here

  • 3 tiers of support, internally

○ T1 — service desk ○ T2 — technology-specific, “User Support” ○ T3 — technology-specific, “App Dev”

  • Vendor support
  • Community support

We don’t have all the answers :(

slide-19
SLIDE 19

Add speaker name here

  • Stand up someone’s local site onto a dev instance
  • Clone environments to-and-fro’
  • Occasional über-specific drush command

○ Actually quite nice!

  • Occasional über-unnecessary drush command

○ Teachable moment

Common requests

slide-20
SLIDE 20

Add speaker name here

So… Where do you draw the line?

“ “

slide-21
SLIDE 21

Add speaker name here

  • Custom Modules

○ We can provide logs!

  • Structures

○ Keep adding extra eyes until it’s figured out

  • Themes

○ Have you tried Drupal Lite?

The line is grey. And dotted. And invisible.

slide-22
SLIDE 22

Add speaker name here

Providing Tech Support to Drupal Devs

Supporting Drupal-as-a-Service

Kyle Hakala

University of Minnesota

Questions?

slide-23
SLIDE 23

Add speaker name here

Join us for the Unconference

Saturday, June 8th, 9:30am-4:30pm

#tcdrupal

slide-24
SLIDE 24

What did you think?

Locate this session on the TC Drupal website:

https://2019.tcdrupal.org/schedule

Leave your feedback

https://2019.tcdrupal.org/feedback