Matt Ström-Awn

One possibility is to take the lead from CSS and allow for a user-agent-defined value through something like `env()`. In this case, you might define a stack of possible user...

As you mentioned in your initial proposal, using the CSS keywords alone would require the parser to have an opinion of how color keywords map to each other between platforms....

I definitely agree that platform-specific variance is necessary, and that the way you've outlined to represent them (multiple JSON files) is the right approach. I think we're puzzling through the...

I think that the typography composite type serves as a good test balloon (or stress test, or canary in the coal mine, maybe) for some of the higher-level ideas about...

If groups and tokens can share a name, my inclination is that the token/group hybrid is the right way to go. However, I think we ought to hash out if...

I'm mostly just toying with two different approaches to the group syntax, which may necessitate a separate issue. So I'm gonna open up a new discussion to continue that thread...

@c1rrus thanks for the clarification! I see the use case and I also want to see if we can accommodate it if possible. The hard part for me is that...

As I dig through the discussions more and more, I'm seeing (just as you are, @mathieudutour) some convergence in the underlying intention of mixins, interfaces, components, and variants. Just like...

I think this could actually be as simple as having a `url` type which follows exactly the [whatwg standard](https://url.spec.whatwg.org/). Urls can be relative paths, which would be combined with a...

I've seen a few conversations where this shape of problem is bubbling up: authors shouldn't be prevented from using features of a platform (like CSS system color keywords) just because...