Teaching Drupal
Upcoming SlideShare
Loading in...5
×
 

Teaching Drupal

on

  • 2,170 views

You know how to use Drupal. You know how to write code, build a theme, and SEO a site. But do you know how to teach others to use Drupal? For every site we create there are clients who must use it, ...

You know how to use Drupal. You know how to write code, build a theme, and SEO a site. But do you know how to teach others to use Drupal? For every site we create there are clients who must use it, many don't know a node from a block. After this session, you will be able to introduce clients to Drupal without freaking them out.

We'll cover:

* Defining "need to know" and emphasizing main concepts
* Thinking like a user, talking like a mentor
* Using normal words with a sprinkling of Drupalese
* Breaking down tasks keeping each user's personality and background in mind
* Translating "my site's broken" into a useful and respectful response
* How to think like a non-geek (for a few minutes)

Statistics

Views

Total Views
2,170
Views on SlideShare
2,170
Embed Views
0

Actions

Likes
0
Downloads
36
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

CC Attribution-ShareAlike LicenseCC Attribution-ShareAlike License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Teaching Drupal Teaching Drupal Presentation Transcript

  • Teaching Drupal Diana Montalion Dupuis 8.24.10 Acquia
  • Teaching DrupalDevelopers: People who spend (a lot of) time figuringout Drupal works, writing code for it, designingthemes for it, reading books about it, and travelingto Drupalcon to talk about it.Users: People forced by circumstances to interactwith Drupal and its developers.DrupalCon Cophenhagen 2010
  • Introduction
  • Introduction* Diana Montalion Dupuis
  • Introduction* Diana Montalion Dupuis* mooncougar (diana: moon goddess + montalion:mountain lion)
  • Introduction* Diana Montalion Dupuis* mooncougar (diana: moon goddess + montalion:mountain lion)* Aaron Forsander (pifantastic)
  • Introduction* Diana Montalion Dupuis* mooncougar (diana: moon goddess + montalion:mountain lion)* Aaron Forsander (pifantastic)* #teachingdrupal
  • You know who he is . . .
  • You know who he is . . .Dries Buytaert: Drupal creator
  • Who is he?
  • Who is he?Tom Standage; Digital Editor for Economist.com
  • Users should be famoustoo!They are the people who use the tools we build andtheir business goals are the reason we do what wedo.
  • Before we start: twoassumptions
  • Before we start: twoassumptions1. Our “user” did not install and build the website.
  • Before we start: twoassumptions1. Our “user” did not install and build the website.2. You did.
  • Before we start: twoassumptions1. Our “user” did not install and build the website.2. You did.2a. Or you could have.
  • Before we start: twoassumptions1. Our “user” did not install and build the website.2. You did.2a. Or you could have.2b. Or you are part of a team who did and/or couldhave.
  • Drupal’s Infamous SteepLearning Curve
  • http://buytaert.net/sites/buytaert.net/files/images/drupal/learning-curve.jpg
  • The User Learning Curve
  • The User Learning Curve“Edit the homepage.”
  • Teaching Drupal Truth #1
  • Teaching Drupal Truth #1The user’s learning curve is steep only if you try todrag them up every mountain.
  • users see these concepts differently than we do: modules, for example
  • We climb mountains
  • We climb mountains* Nodes
  • We climb mountains* Nodes* Blocks
  • We climb mountains* Nodes* Blocks* Views
  • We climb mountains* Nodes* Blocks* Views* Modules
  • We climb mountains* Nodes* Blocks* Views* Modules* Content types
  • We climb mountains* Nodes* Blocks* Views* Modules* Content types* Roles and permissions
  • We climb mountains* Nodes* Blocks* Views* Modules* Content types* Roles and permissions* Taxonomy
  • Users hike paths
  • Users hike paths* Log in
  • Users hike paths* Log in* Edit the About Us page
  • Users hike paths* Log in* Edit the About Us page* Create a blog post
  • Users hike paths* Log in* Edit the About Us page* Create a blog post* Attach a file to a press release
  • Users hike paths* Log in* Edit the About Us page* Create a blog post* Attach a file to a press release* Add a new editor
  • Users hike paths* Log in* Edit the About Us page* Create a blog post* Attach a file to a press release* Add a new editor* Edit the list of tags
  • Users hike paths* Log in* Edit the About Us page* Create a blog post* Attach a file to a press release* Add a new editor* Edit the list of tags* Effectively report a bug
  • Teaching Drupal Truth #2we love mountains (concepts), users hike paths (accomplish tasks)
  • Teaching Drupal Truth #2 We don’t teach Drupal. We teach the user how to do what they need to do, but don’t already know how to do, with the tool we build for them.we love mountains (concepts), users hike paths (accomplish tasks)
  • My favorite userCaitlin Copple: previously of the YWCA of Missoula
  • Where do I begin?
  • Where do I begin?1. Ask, “What do you do on the site?”
  • Where do I begin?1. Ask, “What do you do on the site?”2. Ask, “Have you used Drupal before? Have youused any other web applications?”
  • Where do I begin?1. Ask, “What do you do on the site?”2. Ask, “Have you used Drupal before? Have youused any other web applications?”3. Empathize.
  • Empathy “the action of understanding, being aware of, being sensitive to, and vicariously experiencing the feelings, thoughts, and experience of another ...”IOW, walk in the user’s shoes
  • And remember . . . The user has no context.normal Drupal behavior or a bug?
  • Four essential steps
  • Four essential steps1. Teach.
  • Four essential steps1. Teach.2. Show.
  • Four essential steps1. Teach.2. Show.3. Do.
  • Four essential steps1. Teach.2. Show.3. Do.4. Document.
  • Teach.
  • Teach.1. Explain the task you are about to demonstrate.“Let’s edit the About Us page.” “Let’s create a newblog post.” “Let’s add a new user.”
  • Teach.1. Explain the task you are about to demonstrate.“Let’s edit the About Us page.” “Let’s create a newblog post.” “Let’s add a new user.”2. Use normal words (with a sprinkling of Drupalesewhen necessary.) “Alan has the role of editor, andwe’re going to give that role permission to edit otheruser’s blog posts.”
  • Show.
  • Show.Show the user how to do it. If you can’t be there inperson, use screensharing.
  • Do.
  • Do.1. Ask the user to do it.
  • Do.1. Ask the user to do it.2. Pay attention to where they falter, is there a way tomake the path more clear?
  • Do.1. Ask the user to do it.2. Pay attention to where they falter, is there a way tomake the path more clear?3. Go at their pace, add more challenge whennecessary, stop and rest when it’s beneficial.
  • Document.
  • Document.1. Prepare “just enough” documentation ahead oftime.
  • Document.1. Prepare “just enough” documentation ahead oftime.2. Encourage the user to take notes. This will helpthem remember how to do it or at least, knowwhere to look it up.
  • Document.1. Prepare “just enough” documentation ahead oftime.2. Encourage the user to take notes. This will helpthem remember how to do it or at least, knowwhere to look it up.3. Create a space for communal editing ofdocumentation and a process for asking questions.
  • Teaching Drupal Truth #3yes, I made up the word unfrustrate
  • Teaching Drupal Truth #3 The less time you spend fixing a broken site while unfrustrating the user, the more time you will have to do other the things. Like, code. Win win.yes, I made up the word unfrustrate
  • Geekitis
  • Geekitis1. Going out for a beer is more fun if you discussusing hook_form_alter vs hook_form_FORM_ID_alter.
  • Geekitis1. Going out for a beer is more fun if you discussusing hook_form_alter vs hook_form_FORM_ID_alter.2. In conversation, you mention having spoken togreggles.
  • Geekitis1. Going out for a beer is more fun if you discussusing hook_form_alter vs hook_form_FORM_ID_alter.2. In conversation, you mention having spoken togreggles.3. You hate (or love) camelCase.
  • Geekitis1. Going out for a beer is more fun if you discussusing hook_form_alter vs hook_form_FORM_ID_alter.2. In conversation, you mention having spoken togreggles.3. You hate (or love) camelCase.4. After work, for fun, you work.
  • Geekitis1. Going out for a beer is more fun if you discussusing hook_form_alter vs hook_form_FORM_ID_alter.2. In conversation, you mention having spoken togreggles.3. You hate (or love) camelCase.4. After work, for fun, you work.
  • Teaching Drupal Truth #4
  • Teaching Drupal Truth #4If you have geekitis, it isnt contagious.Users don’t have to love the mountains to effectivelyhike the path. And they don’t care that you climbedEverest unless that solves their immediate problem.
  • Leave a map
  • Leave a map1. Suggest quality resources (books, website links,tutorials).
  • Leave a map1. Suggest quality resources (books, website links,tutorials).2. Provide documentation and encourage the user tocollaborate.
  • Leave a map1. Suggest quality resources (books, website links,tutorials).2. Provide documentation and encourage the user tocollaborate.3. Make sure the user knows who to contact whenproblems arise.
  • Bring the bug repellent
  • Bring the bug repellent1. Take the sting out of bug reporting by trainingusers to give you what you need to solve theproblem. Ask them specific questions and respondto drama with empathy.
  • Bring the bug repellent1. Take the sting out of bug reporting by trainingusers to give you what you need to solve theproblem. Ask them specific questions and respondto drama with empathy.2. Have them walk you through the process.
  • Bring the bug repellent1. Take the sting out of bug reporting by trainingusers to give you what you need to solve theproblem. Ask them specific questions and respondto drama with empathy.2. Have them walk you through the process.3. Make sure they know how to take a screenshot.
  • Teaching Drupal Truth #5
  • Teaching Drupal Truth #5No users; no Drupal. The people who apply ourtools to real-world problems are the reason we areall here today.
  • Teaching Drupal Truths
  • Teaching Drupal Truths1. The user’s learning curve is steep only if you try todrag them up every mountain.
  • Teaching Drupal Truths1. The user’s learning curve is steep only if you try todrag them up every mountain.2. We don’t teach Drupal. We teach the user how todo what they need to do, but don’t already know howto do, with the tool we build for them.
  • Teaching Drupal Truths1. The user’s learning curve is steep only if you try todrag them up every mountain.2. We don’t teach Drupal. We teach the user how todo what they need to do, but don’t already know howto do, with the tool we build for them.3. The less time you spend fixing a broken site whileunfrustrating the user, the more time you will haveto do other the things. Like, code. Win win.
  • Teaching Drupal Truths1. The user’s learning curve is steep only if you try todrag them up every mountain.2. We don’t teach Drupal. We teach the user how todo what they need to do, but don’t already know howto do, with the tool we build for them.3. The less time you spend fixing a broken site whileunfrustrating the user, the more time you will haveto do other the things. Like, code. Win win.4. If you have geekitis, it isnt contagious.
  • Teaching Drupal Truths1. The user’s learning curve is steep only if you try todrag them up every mountain.2. We don’t teach Drupal. We teach the user how todo what they need to do, but don’t already know howto do, with the tool we build for them.3. The less time you spend fixing a broken site whileunfrustrating the user, the more time you will haveto do other the things. Like, code. Win win.4. If you have geekitis, it isnt contagious.5. No users; no Drupal. The people who apply ourtools to real-world problems are the reason we are
  • http://cph2010.drupal.org/node/7243