Documentation Driven Design Systems

9627abc56bc436faecbe45f2645159d6?s=47 Adekunle Oduye
December 04, 2017

Documentation Driven Design Systems

Let’s be real, most of us hate writing documentation. We procrastinate as if it will magically get done on its own, ultimately waiting until the very end of the design process to put something together. When we finally get down to it, the documentation winds up being unclear, confusing and simply not good. So the main question is: How do we make our documentation suck less?

9627abc56bc436faecbe45f2645159d6?s=128

Adekunle Oduye

December 04, 2017
Tweet

Transcript

  1. 6.
  2. 7.
  3. 11.

    Documentation Pain Points • Writing documentation is hard • Documentation

    is last on the list • Documentation written for a specific audience
  4. 13.
  5. 14.
  6. 15.
  7. 21.
  8. 22.
  9. 23.
  10. 24.
  11. 25.
  12. 28.
  13. 29.
  14. 30.
  15. 31.
  16. 32.
  17. 33.
  18. 35.
  19. 36.

    What we learned • Communicate major updates to design systems

    • Validate patterns before release • Make it easier to integrate the style guide into products • More documentation on patterns
  20. 38.
  21. 39.
  22. 40.
  23. 41.
  24. 42.
  25. 43.
  26. 49.

    In Summary: • The anatomy of great documentation • The

    process of creating great documentation • How to socialize great documentation within your team and organization