Baby Got Backend: The Sequel

Why content editors are our most important users ever, why they hate life, and how you can make them happier.

Transcript

1. Baby Got Backend 1
2. why content editors are your most important users ever, why they hate life, and how you can make them happier 2
3. hello! i’m @eaton 3
4. hello! i’m @eaton 3
5. i’m with lullabot 4
6. i’m with lullabot 4
7. strategy + design development + training 5
8. strategy + design development + training 5
9. let’s play a game! 6
10. “ 7 We just got a new CMS, and everyone hates it. Nobody’s getting any work done and we wish we’d been consulted.
11. “ Everyone in the history of internets ever 7 We just got a new CMS, and everyone hates it. Nobody’s getting any work done and we wish we’d been consulted.
12. “ 8 I really love the design, and all the features we wanted are accounted for… …But I’m concerned that our content editors aren’t getting the attention they deserve.
13. “ Nobody with the power to write cheques, ever 8 I really love the design, and all the features we wanted are accounted for… …But I’m concerned that our content editors aren’t getting the attention they deserve.
14. 9 the most important users, ever
15. 10 Content = Sales
16. 10 Content = Sales 30 employees 10 months 0 posts -10% inquiries
17. 11 Content = Time
18. 11 Content = Time 40 engineers 5 forms per week 20 wasted minutes $65,000 per year
19. Content = Reputation 12
20. Content = Reputation 12 1 press release 0 oversight $24 billion losses
21. Content = Reputation 12 1 press release 0 oversight $24 billion losses
22. “ Karen McGrane, Super-Genius 13 If you create content, the usability of your CMS is as important as your eCommerce transaction flow. Most CMS’s look like a database got drunk and vomited all over the screen.
25. we can’t just make it “betterer” 15
27. “ Blake Hall, Lullabot There’s a big difference between ‘site’ and ‘shop’ mentalities. Devs who work on a site for a long time always make some code that no one else can use. 17
28. think tasks not forms 18
29. 19 measuring the pain
30. 19 measuring the pain
31. confused newbies 20
32. Clarity & continuity 21 ⬡ Provide clear prompts ⬡ Label and group fields carefully ⬡ Use defaults and validation ⬡ Reflect what fields really mean ⬡ Stay consistent
35. frustrated power users 24
36. Soothing the editor-beast 25 ⬡ Consolidate multi-step tasks ⬡ Automate bulk operations ⬡ Speed first, looks second ⬡ Accept the need for custom tools
38. expensive accidents 27
39. Adding guardrails 28 ⬡ Label actions clearly ⬡ Provide previews for changes ⬡ Make content states obvious ⬡ Offer scheduling/workflow overviews ⬡ Use confirmation sparingly
41. old content is rotting 30
42. Every node has its day 31 ⬡ Tools to find “archival” content ⬡ Permission to unpublish & delete ⬡ Expose analytics information ⬡ Get buy-in from bosses
46. give editors a voice in the project 34
47. ARE THESE DEV TASKS REALLY UX TASKS?
48. The UX Toolbox ⬡ Study tasks, workflow, mental models ⬡ Interviews and roleplay ⬡ Questionnaires and card sorts ⬡ Prototype, then polish ⬡ Learn from existing patterns 36
49. welie.com developer.yahoo.com/ypatterns ui-patterns.com boxesandarrows.com
50. The Drupal Toolbox ⬡ Lots of node form tools ⬡ Custom views, bulk operations ⬡ Flags, actions, and workflow ⬡ States and permissions ⬡ Yes… custom code. ⬡ Building blocks, not silver bullets 38
51. Ye olde recap 39 ⬡ Clarity & continuity for newbies ⬡ Automation for power users ⬡ Protection from costly mistakes ⬡ Tools for ongoing maintenance ⬡ Fix tasks and workflows, not forms ⬡ Embrace tailored solutions