Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Linear books to open world adventure

370 views

Published on

Joe Pairman at SEMANTICS 2017

Published in: Technology
  • Be the first to comment

Linear books to open world adventure

  1. 1. From Linear Books to an Open World Adventure A case study of taxonomy to drive interactive, personalized reader experiences Joe Pairman
  2. 2. Complex product range, with complex docs to match
  3. 3. Made searchable and scalable through taxonomy
  4. 4. The starting point: legacy, book- oriented XML format (DocBook)
  5. 5. Making content more searchable and helpful
  6. 6. Taskonomy: simplifying by focusing on user tasks
  7. 7. Taskonomy: simplifying by focusing on user tasks Top-level tasks: ~ Bridge roles, tools, and environments ~ Roughly correspond to lifecycle
  8. 8. Top-level tasks used to unify the content
  9. 9. Insight deep in the hierarchy Users needed to see content related to their task…
  10. 10. Insight deep in the hierarchy Users needed to see content related to their task… …detailed procedures but also overviews/ scenarios
  11. 11. Insight deep in the hierarchy Users needed to see content related to their task… …detailed procedures but also overviews/ scenarios
  12. 12. Insight deep in the hierarchy Users needed to see content related to their task… …detailed procedures but also overviews/ scenarios
  13. 13. Re-architecting content: a user goal or session per page / URL
  14. 14. Re-architecting content: a user goal or session per page / URL
  15. 15. Re-architecting content: a user goal or session per page / URL ~ Good for users ~ Good for Google ~ Good for site search/browsing
  16. 16. Focused pages reduce duplication & effort~ From a comprehensive user guide per product
  17. 17. Focused pages reduce duplication & effort~ From a comprehensive user guide per product ~ To a single instance of each task, reducing product-specific instructions to installs, etc.
  18. 18. Focused pages reduce duplication & effort~ From a comprehensive user guide per product ~ To a single instance of each task, reducing product-specific instructions to installs, etc. ~ Even minor differences covered by generalizing or labels
  19. 19. Consistency and efficiency
  20. 20. Talend still need some similar pages
  21. 21. As before, variants managed by “profiling”
  22. 22. Now, profiling sourced from taxonomy
  23. 23. Now, profiling sourced from taxonomy
  24. 24. Now, profiling sourced from taxonomy
  25. 25. Consistent, efficient, and queryable content
  26. 26. Simple recommendations, based on taxonomy
  27. 27. Google often gets users to the right area, but~ there also needed to be relevant links between related pages ~ user may land on: – Wrong product variant / version – Detailed procedures (when they need to understand the system a bit first) ~ user often simply needs to research more for a full picture
  28. 28. Logic for auto related links ~ More relevant than fully automated related links – Human-constructed thesaurus – Human input in tagging ~ Far less creation & maintenance effort than manual links
  29. 29. “Personal books”
  30. 30. Lessons learned
  31. 31. Lessons learned ~ Such rich, granular tagging requires a good team, good training, and a consistent body of content – But it can be achieved by normal human authors ~ Always good to start simple, less coupled, lightly integrated – But know that many content tools are weak at taxonomy/semantics, and plan accordingly ~ Taxonomy and interaction design may well need revisited – Example: expectations around product and module facets
  32. 32. Products and their modules
  33. 33. Products and their modules
  34. 34. Last lesson: there’s always more you can do — once content’s appropriately annotated Version 6.0 Version 6.4 but content is tagged with version, so there’s a base for logic to point Google to the “canonical” page
  35. 35. The result Working with a taxonomy enables us to bridge silos between cross-format, heterogeneous pieces of content. It is the centerpiece of our top-down and bottom-up navigation. Relations between concepts can be leveraged at any stage of the documentation workflow: at authoring time, before publishing and also to check online content. ~ François Violette, Information Architect, Talend
  36. 36. Questions / suggestions?~ joepairman@mekon.com ~ @joepairman

×