how is CSS handled?

[merodiro]

as @nobrayner suggested we need to decide how are we going to handle CSS so we can document it.

things we need to decide:

• are we going to continue with emotion or use tailwind? and are we going to use emotion but have tailwind design system values?
• if we are going to build our design system how are going to handle spacing em or rem or both?
• how will the spacing scale look like?

feel free to add anything I missed

[datner]

My vote is on tailwind

[datner]

I want to use something that as documented well, and is well known so many people have an easy time working with it, also something very opinionated so developers have limited input on convention, reducing overhead and discussions

[JacobMGEvans]

+1 Tailwind

[datner]

@JacobMGEvans don't +1 in the comments, theres a literal voting mechanism in this feature, +1 my comment 😆

[AhmedEldessouki]

My vote goes for emotion. in my opinion and according to what Kent said, ready to use systems might come with limits. in the other hand if we continued with emotion, it will be easy to refactor or improve according to our needs.

I don't have any experience with em but I dont mind using it or both.

I leave the third for i will go with the majority

[AhmedEldessouki]

i do remember the second one. the third i must have missed it. thu im still on the emotion side 😄
thanks for the clarification 👍🏼 🙏🏼

[JacobMGEvans]

We definitely are not using Component Libraries like Material UI lol

[datner]

doesn't like the styled syntax or CSS modules because that forces him to choose a name for everything even when naming doesn't make sense

I agree with this so much. It's the sole reason why I dropped styled-component and didn't ever recommend it to any of my clients

[AhmedEldessouki]

We definitely are not using Component Libraries like Material UI lol

I never said we do 😄 i cleared that later on 😆

[AhmedEldessouki]

doesn't like the styled syntax or CSS modules because that forces him to choose a name for everything even when naming doesn't make sense

I agree with this so much. It's the sole reason why I dropped styled-component and didn't ever recommend it to any of my clients

+1

[merodiro]

My vote is on tailwind mainly because it comes with good defaults so we don't need to have a discussion on em vs rem or picking names for the variables that are meaningful to everyone. and also because it's already documented so we don't have to worry about creating documentation for our custom design system.

[JacobMGEvans]

+1 Tailwind as well