Your SlideShare is downloading. ×
Baby Got Backend (CMS Expo 2011)
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Baby Got Backend (CMS Expo 2011)

1,750
views

Published on


0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

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

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Any content driven site has an internal team that creates and publishes content. These content administrators spend all day using the Drupal interface, even though they’re not developers and they may have no idea how things work under the hood.\n
  • Community driven site has both external and internal content creators. \nPower law. your 1% that's herding the sheep, and your 10% that's actually creating original content.\nAdmins are doing community moderation in addition to managing content.\n
  • \n
  • Drupal 7 provides tons of improved UX widgets!\nTons of modules let you do crazy things!\njQuery widgets and more!\nBlog posts and books on usability!\n
  • Drupal 7 provides tons of improved UX widgets!\nTons of modules let you do crazy things!\njQuery widgets and more!\nBlog posts and books on usability!\n
  • Drupal 7 provides tons of improved UX widgets!\nTons of modules let you do crazy things!\njQuery widgets and more!\nBlog posts and books on usability!\n
  • \n
  • CMS Showdown at SXSW -- drupal was EASIER. wtf?\nrevealed the importance and danger of workflow customization.\ndoes that mean drupal "is easier?" no.\nit means that "your blog" is a crappy way to do forum moderation\n
  • \n
  • No joke: one client has a 40-page document explaining how to post a new page on their site. 40 pages! It suggests starting with a glass of wine. \n\nWhat IS crappy about drupal that better tools don't automatically fix?\nWorkflow, information overload (too much data, too hard to find),\ntoo many fields, too many clicks, too many screens...\n
  • \n
  • \n
  • \n
  • \n
  • If a content-driven organization isn't listening to its content creators -- and giving them a voice in redesign and platforming decisions - they might as well be throwing money down the drain. \n\n
  • If you have analytics, pay attention to them just as ecommerce sites would pay attention to shopping cart analytics. How often to people start creating content and stop, why? For teams, do you know how long it takes them to create content? Where are the problems? What are their pain points? Chances are it's not "Oh, Drupal is ugly." \n\n\n
  • Roleplay, act out the workflow, see where they hang up, see where they grimace. Don't JUST simulate the online stuff, simulate the offline components of their work, too. Where are the roadblocks?\n\n\n\n
  • \n
  • If your system is older than six months, your content creators have probably found uses for it you don't know about.\nMyspace's CSS jammed into profile fields, "Oh, we've been using the Alt text for something else entirely," etc.\n\n
  • \n
  • If it's a new site this even more important -- there's often not enough existing data for people to look for best practices, and they just muck with it until it does what they want it to.)\n
  • \n
  • Keep asking about the "whys" of tasks they do to understand, and avoid rebuilding old frustrations. (Building oysters around pearls is never useful). \n\nThis forces you to think like the business, too, not JUST a coder or designer. \n\n
  • There's a big difference between essential workflow and learned workarounds to old systems. \n\nDelicate balance between presenting them with a better approach than they're used to... and berating them into accepting a solution.\n\n
  • Iterate, iterate, iterate. Fast-and-crappy turns to polished-and-good with time and feedback from the users. \nBuilding content tools without feedback is like optimizing code without without metrics or profiling data. Flying blind.\n\n
  • \n
  • Don't optimize the individual pieces without addressing the workflow. \n\nTrain, simulate, roleplay. Do the intuitive pieces turn baffling when content editors have to pull the pieces together? It's easy to be penny-wise pound-foolish. \n\n\n
  • Drupal's emphasis on metadata and connections between pieces of content makes it easy to miss how mind-boggling the TASK is, because each one of the 15 screens is "easy" \n\n
  • Drupal's emphasis on metadata and connections between pieces of content makes it easy to miss how mind-boggling the TASK is, because each one of the 15 screens is "easy" \n\n
  • Wrapper forms that build and save nodes behind the scenes. \nSingle-step forms to create an episode and a cluster of articles, galleries, etc.\n
  • \n
  • \n
  • Just naming the labels carefully and arranging things in the right tabs is huge. This is a classic UX/IA task. \n\nJust because it’s not a difficult technical problem to solve doesn’t mean it’s not important.\n
  • 'Manage this' works on every page on the WWE site, it just presents context-relevant 'Manage' options.) \nManaging things is the same TASK even if it's different DATA. Admins only care about their tasks.\n
  • Muscle memory and visual patterns are important. NO ONE READS HELP TEXT.\nGrouping implies purpose: having the same groups even when fields differ from site to site\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Lullabot.com - Simple dashboard to see upcoming articles and current live articles\nPanels, Views, Login Destination, Scheduler\n
  • WWE.com - Content editing screen\nVertical Tabs (built into D7), CCK Fields, lots of CSS & JS\nLOTS AND LOTS of time asking, “Should this go here?”\n
  • WWE.com - Bulk unpublishing, tagging, deleting, management of content.\nViews, Views Bulk Operations, Better Exposed Filters, extra CSS\nInterviews with the content team\n
  • Useful resources are all over the place.\n\n
  • Transcript

    • 1. BABY GOT BACKENDContent administrators are users too
    • 2. Hi, I’m@eaton. 2
    • 3. P O W E R E D b y S E R V I C E™ 3
    • 4. “THE SITE SHOULD BE EASY!” …FOR WHO? 4
    • 5. DRUPAL DEVS WORK TO MAKETHINGS EASY FOR BUILDERS
    • 6. THE BUILDERS WORK TO MAKETHINGS EASY FOR VISITORS
    • 7. WHO’S LOOKING OUT FORTHE CONTENT ADMINS?
    • 8. CONTENT CREATORS ARETHE MOST IMPORTANT USERSON YOUR SITE. 8
    • 9. THEY’RE THE PEOPLE WHOUSE YOUR SITE EVERY DAY. 9
    • 10. GOOD NEWS: YOU HAVETONS OF TOOLS! 12
    • 11. 13
    • 12. 13
    • 13. 13
    • 14. 13
    • 15. BAD NEWS: INTERFACE WIDGETSDON’T EQUAL USABILITY 14
    • 16. BETTER WORKFLOWEQUALS USABILITY 16
    • 17. Step 34: Pick up the phone and call Joe, Brooke,Karen or, in a pinch, Doris. Tell them that youve justcreated a new le and it needs to be approvedbefore your work can continue. Once they haveapproved the le, proceed to step 35…
    • 18. DRUPAL PRESENTS A DATAMODEL, NOT A TASK MODEL 18
    • 19. DRUPAL PRESENTS A DATAMODEL, NOT A TASK MODEL 19
    • 20. THE TASK MODEL IS YOUR JOB.DRUPAL PRESENTS A DATAMODEL, NOT A TASK MODEL 19
    • 21. HOW TO DO IT
    • 22. HOW TO DO IT1. Listen to the content administrators. 21
    • 23. 1. Listen to the content administrators.IF YOUR CONTENT CREATORSDON’T HAVE A VOICE, YOU’RETHROWING MONEY AWAY. 22
    • 24. 1. Listen to the content administrators.ANALYZE TASK COMPLETIONLIKE IT’S AN ECOMMERCESHOPPING CART. 23
    • 25. 1. Listen to the content administrators.GET THEM TO ROLEPLAY ANDDOCUMENT BOTH ONLINE ANDOFFLINE WORKFLOWS. 24
    • 26. HOW TO DO IT1. Listen to the content administrators.2. Don’t just understand the data, understand what they’re doing with it. 25
    • 27. 2. Don’t just understand the data, understand what they’re doing with it.CONTENT CREATORS INVENT ALLKINDS OF WORKAROUNDS. 26
    • 28. 2. Don’t just understand the data, understand what they’re doing with it.UNDERSTANDING HOW FIELDSARE USED WILL SAVE COUNTLESSHOURS CLEANING UP MESSES. 27
    • 29. 2. Don’t just understand the data, understand what they’re doing with it.EVEN NEW SITES EVOLVEQUICKLY. 28
    • 30. HOW TO DO IT1. Listen to the content administrators.2. Don’t just understand the data, understand what they’re doing with it.3. Keep asking “why?” and iterate, iterate, iterate. 29
    • 31. 3. Keep asking “why?” and iterate, iterate, iterateTHINK LIKE THE BUSINESS.WHY DO THEY NEED TO DO ACERTAIN TASK? 30
    • 32. 3. Keep asking “why?” and iterate, iterate, iterateDON’T JUST REPLICATE EXISTINGMENTAL MODELS. 31
    • 33. 3. Keep asking “why?” and iterate, iterate, iterateFAST-AND-CRAPPY TURNS TOPOLISHED-AND-GOOD WITH THERIGHT FEEDBACK. 32
    • 34. HOW TO DO IT1. Listen to the content administrators.2. Don’t just understand the data, understand what they’re doing with it.3. Keep asking “why?” and iterate, iterate, iterate.4. Optimize the workflow, not individual screens. 33
    • 35. 4. Optimize the workflow, not individual screens.REAL CONTENT PRODUCTIONIS A PROCESS, NOT A SINGLESCREEN. 34
    • 36. 4. Optimize the workflow, not individual screens.METADATA MAKES FOR EASYINTERFACES AND COMPLEXWORKFLOWS. 35
    • 37. 4. Optimize the workflow, not individual screens.GIVE USERS CONTEXT(BREADCRUMBS, DASHBOARDS,PREVIEWS...) 36
    • 38. 4. Optimize the workflow, not individual screens.STREAMLINE & AUTOMATEAROUND CONFUSION: TREATDEFAULT FORMS AS POWERTOOLS. 37
    • 39. 4. Optimize the workflow, not individual screens.BULK TOOLS.EASY TURNS HARD WHEN YOUHAVE TO REPEAT IT 10,000 TIMES. 38
    • 40. HOW TO DO IT1. Listen to the content administrators.2. Don’t just understand the data, understand what they’re doing with it.3. Keep asking “why?” and iterate, iterate, iterate.4. Optimize the workflow, not individual screens.5. Use repeating concepts, not just UI elements. 39
    • 41. 5. Use repeating concepts, not just UI elements.PROPER CATEGORIZATION ANDCONSISTENT LABELING GO ALONG WAY. 40
    • 42. 5. Use repeating concepts, not just UI elements.USE SIMILAR VISUAL CUES FORWORKFLOWS ACROSS THE SITE. 41
    • 43. 5. Use repeating concepts, not just UI elements.PLACE SIMILAR FIELDS IN ACONSISTENT PLACE ACROSSALL SCREENS. 42
    • 44. NIRVANA! …ALMOST. 43
    • 45. THE BETTER IT FITS ONE TEAM,THE HARDER IT IS TO REUSE. 44
    • 46. “There’s a big difference between the ‘site’ and‘shop’ mentalities.Devs who work on a site for a long time alwaysmake some code that no one else can use.Shops and the Drupal community usually makestuff that can be reused over and over. Blake Hall 45
    • 47. HOW TO DO IT1. Listen to the content administrators.2. Don’t just understand the data, understand what they’re doing with it.3. Keep asking “why?” and iterate, iterate, iterate.4. Optimize the workflow, not individual screens.5. Use repeating concepts, not just UI elements.6. Accept that many good answers will be unique. 46
    • 48. Thanks!http://lb.cm/backend 47
    • 49. 48
    • 50. SUPER EXTRABONUS SLIDES 49
    • 51. 50
    • 52. 51
    • 53. 52
    • 54. welie.com ui-patterns.comdeveloper.yahoo.com/ypatterns boxesandarrows.com 53

    ×