Re: [community-group] Should composites be part of the MVP specification? (#54)

I find **color pairs** powerful, particularly for enabling development accessibility tooling like contrast checking.

A current typedef I'm using for fg/bg color pair tokens is specific to the naming and tooling in our system e.g. { Color: color, OverSurface: color, ForText: boolean }. ForText is used to render the token as "Aa" over the OverSurface color instead of just a colored dot.

If no composite types are included in the spec then in our case we'd probably be waiting for a tool vendor like Figma (or a well integrated plugin) to adopt the spec and implement their own specific typedef for color pairs and then either have an automated translation between our typedef and theirs or adapt our typedef in source to match theirs.

The motivating factor to translate or adapt would be better display and selection of tokens within their interface.

Being outside the javascript ecosystem we'd be implementing the generated docs and consumer code ourselves in lua so wouldn't be as influenced by a community npm package.

**Text styles** are also something that I typically author, display, and consume as bundle of tokens, so add a **+1** to including that if there are any composites defs that get added to the spec.

-- 
GitHub Notification of comment by rfrey-rbx
Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/54#issuecomment-949974567 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 22 October 2021 21:40:05 UTC