Confusing Returnings of Server Side Rendering API about css HOT 6 CLOSED

@JacobLinCool Sorry for the confusion caused by the old documentation, I will explain all this later with the new documentation.

Our new documentation face will be updated soon. 🤩 Stay tuned.

from css.

@1aron Thanks for your response.

I understand the concepts behind the pre-generating strategy, but it seems not a good idea to use Master CSS variables within native CSS? Master CSS variables are more likely the internal (private) ones to me and should not be accessible by other parties.

If I have to share variables within and without Master CSS, maybe I would like to control the state by myself.

from css.

@JacobLinCool This issue has been sorted into milestone. 😌 https://github.com/master-co/css/milestone/1

from css.

@JacobLinCool I think we might go with your idea - the preset will map colors and inline the rgb into CSS rules, for a minimal output.

Thx again. 😌

from css.

@JacobLinCool About the color tree shaking, let me explain first.
In the future we will have three modes:

1. Map colors directly, inline rgb in CSS rules ( minimal output )
2. Generate the CSS color variables according to the used colors
3. Pre-generate all CSS color variables ( currently preset )

Why use CSS Variables for this? For now, most people still write CSS rules for some reason, so if you want to access the Master's colors, you must go through CSS variables.

from css.

@JacobLinCool Agree, so there will be three modes for you to choose.

If you want to use Master Colors in CSS files and we didn't pre-generated CSS variables for you, you have to look up the color table and define the variables manually, which will reduce the development experience.

Other CSS frameworks don't do this, so people keep raising this issue.

from css.