Travis Spomer

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...

We can't call it a "manifest" because that means something entirely different. A manifest is a list of cargo. In software it means [a file that either lists or describes...

One issue I see is that this would only allow you to track changes made in a single tokens file. But let's say you have a global tokens file, and...

Would the `$metadata` node be sufficient for this, or is it important for what you want that there be a standardized place for specifically an array of tag names as...

`$extensions` can go on tokens—I'd say probably 95% of its use case would be on tokens. To me, all of those things you mentioned make a *lot* more sense as...

Yep, I mixed up `$metadata` with `$extensions`!

I think you missed something there—my proposal is exactly the set of high contrast accessibility colors that are defined in the CSS spec, not just random words. I'm not sure...

I'm sure other platforms have a bunch. But even if there weren't, sometimes things aren't just a solid, fixed color: just on Windows, you have these and more: * The...

Hmm, what would be an advantage of that over using just the CSS keywords? That would increase the parsing complexity of the format, and shift the responsibility of knowing each...

Got it. Platform-specific variances will be necessary for all types of tokens, though, so those need a solution that's not specific to system colors. For example, maybe your text needs...