Great! Thank you for the demos!

That’s three items to cross off my giant Figma feature wishlist

This seems useful for people designing for different screen sizes but it’s quite a lot of clicks during the set up

How are the font-size primitives in your example decided on? for instance is font-size-400 just in your font size scale? and it also looks like the scale starts from 300?

can we get access to the file to check the variables and tokens?

@PyetroRapp

Ай бұрын

Yes please, can you make this file available to study over it?

I can’t think of a use case for primitive/semantic variables at the typography level. Somehow I easily get it for color scales, but can’t think of a use case in type. Anyone have a good example where it would be helpful? As far as I can tell, the primitives would just result in cataloging some of the *unused* type styles and semantic would have your full type scale that’s being used in the CSS (h1, h2…)

I work at a place where we have 6 responsive breakpoints, and 18 brands, how can we set up typography variables to mode swap easily?

Typography variables are BROKEN, as it does not accept % values for lettering space or line-height! Very frustrating :/

💥

So you still need to create a style for a gradient. I hoped that the gradient would be the variable …. I can see that is complicated to build. Still happy with this.

As long as the gradient itself cannot be defined as variables, it makes no sense to claim that variables would now support gradient ihmo

when

this is kind of confusing actually

@paulXmbingu

2 ай бұрын

That is how things work during Front-end development and now they are trying to bridge the gap

@Djerique

2 ай бұрын

@seeamahmod Why?

🧐

Providing too much inheritance and relations also creates confusion of being complexity in design.