Usability for site builders and administrators

One size fits all?
Core conversation at DrupalCon Dublin 2016 about UX and UI.
https://events.drupal.org/dublin2016/sessions/one-size-fits-all-usability-site-builders-and-administrators

Transcript

2. One size fits all? Usability for site builders and administrators Antje Lorch ifrik Core Conversation https://events.drupal.org/dublin2016/sessions/one-size-fits-all-usability-site-builders-and-administrators
3. Usability for site builders and for advanced administrators is neglected. But we can change that.
4. Who? Why? How to solve this
5. about me Antje Lorch @ ifrik  site builder  since Drupal 4.7  freelancer, on my own or in small teams  biologist and scientific editor  Documentation working group and usability
6. about you?
7. Personas: Site builders, front enders & advanced administrators
8. The site builder building websites for others to use  often in a team with backend developers, frontenders ad/or designers  working with core and contrib  finding and appling patches  managing configuration  preparing the site for other user roles on the production site
9. The frontender preparing the site to match the design  configuring display modes  placing blocks  configuring image styles  often in cooperation with sitebuilders and designers
10. The advanced administrator working on the production site  managing content and users  changing UI text: in blocks, messages, automated emails  adding or disabling menu items  disabling blocks  adding forms  without constant access to a sitebuilder or themer
11. Site builders and administrators who can structure their sites are Drupal's super-users.
12. UX problems
13. Results of bad usability  Frustration and wasted time  Unnecessary workaround & over-complication  Security problems
14. What makes bad usability?  Not finding things, overlooking options  Lack of documentation  Assuming instead of knowing  Inconsistent User interface (UI)  Hard-coded work flows  Unclear requirements
15. Five examples
16. Finding pages
17. Where are the permissions? “I can never, ever remember where roles and permissions are when I need to find them, get it wrong every time.” catch #2695771
18. #2701795 Where is migrate?
19. How do you find admin pages of a new module? I check the routing.yml file.
20. Consistency & UI text
21. Path: with or without / ? /blocks /shortcut /menu views ckeditor
22. Deleting or not deleting? #2806651
23. Configure menu items? #2520232
24. … and more  DevDays session “There's a setting for that, wasn't there, somewhere?  http://milan2016.drupaldays.org/node/121
25. Where does bad UX come from?  lack of guidance and standards  assumptions about how Drupal will be used  not enough user testing  as a result of user testing
26. Who is to blame? User 1
28. “We need to fix this”  UI changes to make the admin accessible,  but no strategy for a progressive disclosure  making it even harder to understand how Drupal works
29. How about user 2? starting with less, becoming proficient
30. ...and then we can concentrate on UI standards.
31. We need UI standards for: ➢Consistent behaviour ➢UI texts ➢Placing admin pages
32. Consistency
33. achiving UI consistency for first time users to developers  no one-off fixes, no anti-patterns  checking whether the same problem exist somewhere else  document UI decissions
34. UI texts
35. UI and help texts What do users need where? What I need how often where to understand the concept once on help page and online documentation as a reminder a few times on admin pages to choose the right tickbox, field, format etc when I use it labels and field help
36. Placing pages
37. “I just want to have everything together.”
38. Site building & Theming
39. Content creation & editing
40. Site building Theming
41. “I just need to edit that block...”
42. “Sure, I just change the permissions….”
44. re-organising admin structure  based on personas and use  simple set of questions #2755613
45. For usability we need UI standards Consistency UI text guidance Page structure
46. JOIN US FOR CONTRIBUTION SPRINTS First Time Sprinter Workshop - 9:00-12:00 - Room Wicklow2A Mentored Core Sprint - 9:00-18:00 - Wicklow Hall 2B General Sprints - 9:00 - 18:00 - Wicklow Hall 2A
47. Evaluate This Session THANK YOU! events.drupal.org/dublin2016/schedule WHAT DID YOU THINK?