- From: Ryan Johnson via GitHub <sysbot+gh@w3.org>
- Date: Sun, 04 Sep 2022 03:28:35 +0000
- To: public-design-tokens-log@w3.org
* I refer to the `*.tokens.json` file as the **"manifest"**, because it provides metadata about design tokens, but doesn't represent their final form after transformation. * I refer to the bundle of assets consumed downstream as the **"tokens package"**, which includes the manifest along with associated assets (SVGs, fonts, and other binary file formats). I don't use the term "source" because the manifest could be built in a variety of ways: 1. verbatim as manually-written JSON 2. compiled from manually-written _source_ files (JSON, JSON5, YAML, TS, etc.) 3. managed from within design software (Figma, Sketch, Adobe suite, etc.), either directly or via plugins 4. generated from a database via a programmatic API 5. etc. -- GitHub Notification of comment by CITguy Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/164#issuecomment-1236244447 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 4 September 2022 03:28:37 UTC