View
9.623
Download
1
Category
Tags:
Preview:
DESCRIPTION
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
Citation preview
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 carefully
These people:• Are quick to learn
new systems• Understand
complex user interfaces
• Perform tasks quickly and look for efficiencies
Not technical
Highly technic
alCMS skill level
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
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
Value
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
http://www.wunderkraut.com/sites/wunderkraut.com/files/field_ns_blog_post_attach/captaindrupal_flying.png
Tip #1: Don’t settle for core!
http://blog.amazeelabs.com/en/periodic-table-drupal-modules-infographic
Recommended modules1. Views Bulk Operations with
Administration views2. Administration menu3. WYSIWYG4. LinkIt5. Login destination6. Admin theme - Shiny
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
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!
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 window2. Find the page you want to link to3. Copy node ID (ideally) or path alias4. Create a regular hyperlink
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 process?●What do you love or hate about your
current CMS?
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: 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
2 3
1 1.Title2.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.Author6.Intro: Text that
appears before the body
7.Body: The main page contents
1
5
6
7
4
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○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
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 Edit2. Scroll down and
click publishing options tab
3. Untick promote4. 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 process1. Set up a base build with contrib2. Ask questions 3. Name things well4. Write good help text5. Use contextual links and make custom
ones6. Don’t forget about common sense7. Peer review pays dividends
It will only get better! And easier!
Content editors are the most important users of
your website(Jeff Eaton says so)
Questions?
Contactpam@previousnext.com.au
@pameeela
Recommended