Open Shrinks99 opened 3 months ago
Should we abandon "t-shirt sizing" for type? Numbers are probably more consistent? I've kept it for weight because that already has enforced numbers, but maybe we should abandon them for all of the other options too and create our own mappings?
Proposal
A two-tiered system with primitives (scale) and component (semantic) level tokens. Because theming isn't as much of a consideration with text, we can get away with just two here?
type-tracking-xs
,type-linespace-md
type-size-4xl
,type-weight-500
button-standard-text
,list-label-text
, ``