Documenting Components: Prioritizing content for design, dev & beyond
by Nadia Kaakati

Date posted:

Building a component library may be the ‘what’ of your Design System, but documenting those components provides context around the ‘when’, ‘how’ and ‘why’. But how much information is too much? What content should you prioritize? What about serving different audiences - designers, developers, QA, business? Nadia will address these questions plus share some tips, tricks, and lessons learned from spinning up a Design System at a large organization.

Tags: presentation, chapter-toronto, documentation