- From: Jerome Farnum via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Sep 2022 11:26:08 +0000
- To: public-design-tokens-log@w3.org
> We call them "token JSON" or "token source files." Collectively they're the "source of truth." When we distinguish between files in this format and our original format, we use phrases like "W3C token JSON" (or, if you're trying to be funny, "DTF file") and "proprietary token JSON." > > After being processed by tools, we produce "the generated code" and that goes to NPM in "token packages." So, a very different definition of "token package" than Jerome mentioned a few comments up! Actually, I don’t think your packages and our packages are all that different. Our token packages actually end up as NPM packages, and include the rendered token documents in a `dist` folder, token source files in a `src` folder, and theme and build config files at the root of the package (alongside a README and pretty thumbnail images). This allows projects using our tokens to either import the prebuilt token documents directly, or import a subset (or all) of the token source files for use in their own token packages. -- GitHub Notification of comment by jeromefarnum Please view or discuss this issue at https://github.com/design-tokens/community-group/issues/164#issuecomment-1252214418 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 September 2022 11:26:10 UTC