Your SlideShare is downloading. ×
0
For the love of the content
editors
By Pamela Barone
@pameeela
May 15, 2014
Build better websites and get
happier clients by showing
some love for the content
editors!
Client PM
Content
editors
Developers
?
Who are these people?
These people:
• Don’t have much
web experience
• Are easily confused
and lack
confidence
• Perform tasks very
slowly and c...
These people:
• Have a lot of other
things to do besides
update the website
• Rarely log in
• Get frustrated when
they can...
Or, what’s in it for me?
Content editors and you
(Insert horror story here)
‘It works’ is not enough for a
CMS.
Ease of use / Efficiency
V
a
l
u
e
If they hate to use it, they
won’t use it
(And they will say bad
things about you)
Client PM
Content
editors
Developers
Why don’t we always do
it?
At the end, it’s too late
So let’s start at the
beginning
by building usability into
the process
//www.wunderkraut.com/sites/wunderkraut.com/files/field_ns_blog_post_attach/captaindrupal_flying.p
Tip #1: Don’t settle for
core!
http://blog.amazeelabs.com/en/periodic-table-drupal-modules-infographic
Recommended modules
1. Views Bulk Operations with Administration
views
2. Administration menu
3. WYSIWYG
4. LinkIt
5. Logi...
1. VBO with Administration Views
Drupal core:
• Two options for filtering
• Clunky to use (one at a
time)
• No keyword sea...
VBO with Administration Views
admin/people
Drupal core:
• More clunky filters
• Filter by permission??
• No additional opt...
Bulk operations?
2. Administration menu
(Comes with Administration Menu Toolbar Style)
With some basic options enabled
3. WYSIWYG
Including Spell Check As You Type!
4. LinkIt
Embedding internal links without LinkIt:
1. Open a new window
2. Find the page you want to link to
3. Copy node ...
LinkIt
5. Login destination
Default login: user profile
page
Login destination
Pick a better page!
6. Shiny
admin
theme
Tip #2: Ask questions
Ask questions – any questions
● What is the typical content workflow?
● What are the biggest pain points in the
current pr...
Tip #3: Naming things is
hard – so make a plan for it!
Naming things is hard
● Leverage existing terminology
● Establish consistent labels for content types and
fields
○ Teaser:...
2 3
1 1. Title
2. Thumbnail: Image
that appears on index
pages
3. Teaser: Text that
appears on index
pages
4. Feature imag...
Tip #4: Help text is your
greatest weapon
Write good help text
• Good help text should:
○ describe where the field output will appear
○ answer any obvious questions...
Bad: No additional
information
Bad: Confusing
information
From bad to good
From good to great
Using features for config?
Bonus!
Writing help text can highlight
problems
Copy and paste to create how-to
guides
Tip #5: Contextual links
– Drupal FTW
In-place administration
Tip #5a: Custom
contextual links – there’s
a module for that
Without custom links
1. Click Edit
2. Scroll down and click
publishing options tab
3. Untick promote
4. Save
With custom links
1. Click Remove content from front page
More custom links
Tip #6: Use common sense
1
3
2 1
2
3
Field order matches display
3
2
1
4
5
1
2
5
3
4
But not
anymore :(
Simplify!
Don’t need
Doesn’t work
Tip #7: You build it, you try it
● Have you tried it?
http://www.flickr.com/photos/briandewitt/2391424578/
Build it into your process
1. Set up a base build with contrib
2. Ask questions
3. Name things well
4. Write good help tex...
It will only get better!
And easier!
Content editors are the most
important users of your
website
(Jeff Eaton says so)
Questions?
Contact
pam@previousnext.com.au
@pameeela
For the love of the content editors – jam's Drupal Camp session by Pamela Barone
For the love of the content editors – jam's Drupal Camp session by Pamela Barone
For the love of the content editors – jam's Drupal Camp session by Pamela Barone
For the love of the content editors – jam's Drupal Camp session by Pamela Barone
Upcoming SlideShare
Loading in...5
×

For the love of the content editors – jam's Drupal Camp session by Pamela Barone

9,629

Published on

So, you're building a content management system - let's talk about the content managers!

Simply, it's in the best interest of the vendor to deliver a product that people don't hate to use. Especially if the client doesn't seem to care, it can be really easy to ignore the issue of usability. But even though they may not care during development, they will be made to care once it's delivered.

There are a lot of simple things you can do to make life easier for these users, and it doesn't require major customisation. In addition to increasing client satisfaction, it can also make training easier, and reduce support requests that come from not understanding the system.

In this session, I'll talk about:
Who content editors are, and why they are worth your time
Specific modules and configuration options that can make life easier
Some general guidlelines and processes you can apply (right now!) to improve usability

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
9,629
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "For the love of the content editors – jam's Drupal Camp session by Pamela Barone"

  1. 1. For the love of the content editors By Pamela Barone @pameeela May 15, 2014
  2. 2. Build better websites and get happier clients by showing some love for the content editors!
  3. 3. Client PM Content editors Developers ?
  4. 4. Who are these people?
  5. 5. These people: • Don’t have much web experience • Are easily confused and lack confidence • Perform tasks very slowly and carefully These people: • Are quick to learn new systems • Understand complex user interfaces • Perform tasks quickly and look for efficiencies Not technical Highly technica l CMS skill level
  6. 6. These people: • Have a lot of other things to do besides update the website • Rarely log in • Get frustrated when they can’t remember how to do stuff These people: • Spend most of the day using the CMS • Perform the same tasks over and over • Get frustrated with inefficiency Almost never Almost alwaysCMS use level
  7. 7. Or, what’s in it for me? Content editors and you
  8. 8. (Insert horror story here)
  9. 9. ‘It works’ is not enough for a CMS. Ease of use / Efficiency V a l u e
  10. 10. If they hate to use it, they won’t use it (And they will say bad things about you)
  11. 11. Client PM Content editors Developers
  12. 12. Why don’t we always do it?
  13. 13. At the end, it’s too late
  14. 14. So let’s start at the beginning by building usability into the process
  15. 15. //www.wunderkraut.com/sites/wunderkraut.com/files/field_ns_blog_post_attach/captaindrupal_flying.p
  16. 16. Tip #1: Don’t settle for core!
  17. 17. http://blog.amazeelabs.com/en/periodic-table-drupal-modules-infographic
  18. 18. Recommended modules 1. Views Bulk Operations with Administration views 2. Administration menu 3. WYSIWYG 4. LinkIt 5. Login destination 6. Admin theme - Shiny
  19. 19. 1. VBO with Administration Views Drupal core: • Two options for filtering • Clunky to use (one at a time) • No keyword search VBO Admin view: • Title search • Better filters • Add your own filters! admin/content
  20. 20. VBO with Administration Views admin/people Drupal core: • More clunky filters • Filter by permission?? • No additional options VBO admin views: • Username, email search • Filter by role • Add your own filters!
  21. 21. Bulk operations?
  22. 22. 2. Administration menu (Comes with Administration Menu Toolbar Style)
  23. 23. With some basic options enabled 3. WYSIWYG Including Spell Check As You Type!
  24. 24. 4. LinkIt Embedding internal links without LinkIt: 1. Open a new window 2. Find the page you want to link to 3. Copy node ID (ideally) or path alias 4. Create a regular hyperlink
  25. 25. LinkIt
  26. 26. 5. Login destination Default login: user profile page
  27. 27. Login destination Pick a better page!
  28. 28. 6. Shiny admin theme
  29. 29. Tip #2: Ask questions
  30. 30. Ask questions – any questions ● What is the typical content workflow? ● What are the biggest pain points in the current process? ● What do you love or hate about your current CMS?
  31. 31. Tip #3: Naming things is hard – so make a plan for it!
  32. 32. Naming things is hard ● Leverage existing terminology ● Establish consistent labels for content types and fields ○ Teaser: Brief description of this item that appears on other pages that reference this item ○ Intro: Brief description of the item that appears on the top of this page above the main content
  33. 33. 2 3 1 1. Title 2. Thumbnail: Image that appears on index pages 3. Teaser: Text that appears on index pages 4. Feature image: Image that appears at the top of the page underneath the title 5. Author 6. Intro: Text that appears before the body 7. Body: The main page contents 1 5 6 7 4
  34. 34. Tip #4: Help text is your greatest weapon
  35. 35. Write good help text • Good help text should: ○ describe where the field output will appear ○ answer any obvious questions ○ list any limitations or requirements ● Bad help text: ○ provides no additional information ○ provides confusing information ○ does not provide information that is required to understand how to use this field ○ is often worse than no help text
  36. 36. Bad: No additional information
  37. 37. Bad: Confusing information
  38. 38. From bad to good
  39. 39. From good to great
  40. 40. Using features for config?
  41. 41. Bonus! Writing help text can highlight problems Copy and paste to create how-to guides
  42. 42. Tip #5: Contextual links – Drupal FTW
  43. 43. In-place administration
  44. 44. Tip #5a: Custom contextual links – there’s a module for that
  45. 45. Without custom links 1. Click Edit 2. Scroll down and click publishing options tab 3. Untick promote 4. Save
  46. 46. With custom links 1. Click Remove content from front page
  47. 47. More custom links
  48. 48. Tip #6: Use common sense
  49. 49. 1 3 2 1 2 3 Field order matches display
  50. 50. 3 2 1 4 5 1 2 5 3 4 But not anymore :(
  51. 51. Simplify! Don’t need Doesn’t work
  52. 52. Tip #7: You build it, you try it
  53. 53. ● Have you tried it? http://www.flickr.com/photos/briandewitt/2391424578/
  54. 54. Build it into your process 1. Set up a base build with contrib 2. Ask questions 3. Name things well 4. Write good help text 5. Use contextual links and make custom ones 6. Don’t forget about common sense 7. Peer review pays dividends
  55. 55. It will only get better! And easier!
  56. 56. Content editors are the most important users of your website (Jeff Eaton says so)
  57. 57. Questions? Contact pam@previousnext.com.au @pameeela
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×