Financial-Times
Content request: Component introduction to improve design/engineer handover
Nowhere on origami.ft.com do we introduce key component features like our typographic scale, named spaces, colour palettes / colour usecases. They're left for an engineer to discover by browsing components in the registry. This makes design/engineering hand-over more tricky, especially when working with someone less familiar with Origami - we need engineering focused design system guidelines that link to component documentation (readme/sassdoc).
It's likely content will be repeated across origami.ft.com (this proposed content), individual component readme files, and the design system guidelines. I see this content being in one place in the future like Carbon
We still want to do this. It's not currently an OKR for this quarter. We think it's a bigger piece of work which involves a broader documentation review/overhaul