Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
For the love of the content editors
By Pamela Barone
@pameeela
September 25, 2013
Build better websites and get happier
clients by showing some love for the
content editors!
Who are these people?
These people:
•  Don’t have much
web experience
•  Are easily confused
and lack confidence
•  Perform tasks very
slowly and...
These people:
•  Have a lot of other
things to do besides
update the website
•  Rarely log in
•  Get frustrated when
they ...
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)
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
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. ...
1. VBO with Administration Views
Drupal core:
•  Two options for filtering
•  Clunky to use (one at a time)
•  No keyword s...
VBO with Administration Views
admin/people
Drupal core:
•  More clunky filters
•  Filter by permission??
•  No additional o...
2. Administration menu
(Comes with Administration Menu Toolbar Style)
With some basic options enabled
3. WYSIWYG
Including Spell Check As You Type!
4. LinkIt
Embedded internal links without LinkIt:
1.  Open a new window
2.  Find the page you want to link to
3.  Copy nod...
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 pro...
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
○  Tease...
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 questio...
Bad: No additional information
Bad: Confusing information
From bad to good
Duh!
Oh, so that’s what it does!
From good to great
Clear enough...
Description plus a tip!
Using features for config?
Bonus!
Writing help text can reveal issues that
need fixing
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 :(
Turn off stuff you don’t need!
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...
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
THANK YOU!
Feedback please!
Locate this session at the DrupalCon
Prague website:
http://prague2013.drupal.org/node/933
Cli...
For the love of the content editors - DrupalCon Prague
For the love of the content editors - DrupalCon Prague
For the love of the content editors - DrupalCon Prague
Prochain SlideShare
Chargement dans…5
×

For the love of the content editors - DrupalCon Prague

1 006 vues

Publié le

https://prague2013.drupal.org/session/love-content-editors

The devil is in the details when creating a content management system, but it's the details that often get left out.

Client cares about how the site looks; developer cares about how the code looks. But rounded corners and nicely commented code don't help the poor content editors.

WHY SHOULD I CARE?

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.

As a former content editor I can attest to this! Ignored we were, until the day came when we had to use the thing. Day after day, we slogged through it, cursing the evildoers (i.e. 'the vendor' and 'the project lead') who inflicted this torture upon us!

WHAT CAN I DO ABOUT THAT?

You can help! And it's not even that hard, or expensive!

Out of the box, Drupal is... OK for content editors. But oftentimes post-major-development, it's... bad.

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

A few basic guidelines for your team can produce a hugely better result. So it's easy, it's valuable, and it makes people happy - how could you say no to that?

Topics to be covered include:
* Ask the right questions before you build
* Help text is your greatest weapon
* Contextual links - check the permissions dummy!
* Advanced content search was not a requirement because it was assumed to exist
* So you developed it - have you ever tried to use it?

And much more!

Publié dans : Technologie
  • Soyez le premier à commenter

For the love of the content editors - DrupalCon Prague

  1. 1. For the love of the content editors By Pamela Barone @pameeela September 25, 2013
  2. 2. Build better websites and get happier clients by showing some love for the content editors!
  3. 3. Who are these people?
  4. 4. 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 technicalCMS skill level
  5. 5. 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
  6. 6. Or, what’s in it for me? Content editors and you
  7. 7. (Insert horror story here)
  8. 8. ‘It works’ is not enough for a CMS. Ease of use / Efficiency V a l u e
  9. 9. If they hate to use it, they won’t use it (And they will say bad things about you)
  10. 10. Why don’t we always do it?
  11. 11. At the end, it’s too late
  12. 12. So let’s start at the beginning by building usability into the process
  13. 13. Tip #1: Don’t settle for core!
  14. 14. http://blog.amazeelabs.com/en/periodic-table-drupal-modules-infographic
  15. 15. Recommended modules 1.  Views Bulk Operations with Administration views 2.  Administration menu 3.  WYSIWYG 4.  LinkIt 5.  Login destination 6.  Admin theme - Shiny
  16. 16. 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
  17. 17. 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 filter!
  18. 18. 2. Administration menu (Comes with Administration Menu Toolbar Style)
  19. 19. With some basic options enabled 3. WYSIWYG Including Spell Check As You Type!
  20. 20. 4. LinkIt Embedded 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
  21. 21. LinkIt
  22. 22. 5. Login destination Default login: user profile page
  23. 23. Login destination Pick a better page!
  24. 24. 6. Shiny admin theme
  25. 25. Tip #2: Ask questions
  26. 26. 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?
  27. 27. Tip #3: Naming things is hard – so make a plan for it!
  28. 28. Naming things is hard ●  Leverage existing terminology ●  Establish consistent labels for content types and fields ○  Teaser: Brief description of the item that appears on other pages that reference this page ○  Intro: Brief description of the item that appears on the top of the page above the main content
  29. 29. 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
  30. 30. Tip #4: Help text is your greatest weapon
  31. 31. 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
  32. 32. Bad: No additional information
  33. 33. Bad: Confusing information
  34. 34. From bad to good Duh! Oh, so that’s what it does!
  35. 35. From good to great Clear enough... Description plus a tip!
  36. 36. Using features for config?
  37. 37. Bonus! Writing help text can reveal issues that need fixing Copy and paste to create how-to guides
  38. 38. Tip #5: Contextual links – Drupal FTW
  39. 39. In-place administration
  40. 40. Tip #5a: Custom contextual links – there’s a module for that
  41. 41. Without custom links 1.  Click Edit 2.  Scroll down and click publishing options tab 3.  Untick promote 4.  Save
  42. 42. With custom links 1.  Click Remove content from front page
  43. 43. More custom links
  44. 44. Tip #6: Use common sense
  45. 45. 1 3 2 1 2 3 Field order matches display
  46. 46. 3 2 1 4 5 1 2 5 3 4 But not anymore :(
  47. 47. Turn off stuff you don’t need!
  48. 48. Tip #7: You build it, you try it
  49. 49. ●  Have you tried it? http://www.flickr.com/photos/briandewitt/2391424578/
  50. 50. 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
  51. 51. It will only get better! And easier!
  52. 52. Content editors are the most important users of your website (Jeff Eaton says so)
  53. 53. Questions? Contact pam@previousnext.com.au @pameeela
  54. 54. THANK YOU! Feedback please! Locate this session at the DrupalCon Prague website: http://prague2013.drupal.org/node/933 Click the “Take the survey” link

×