Twitter | Search | |
Brent Jackson
I would love to see more standardization around how theming is handled in React so I started a theme specification (which isn't coupled to Styled System). Tell me what's missing or why you wouldn't adopt something like this
Style props for rapid UI development
Brent Jackson Brent Jackson @jxnblk
Reply Retweet Like More
Brent Jackson 21 Mar 19
Replying to @jxnblk
Reply Retweet Like
Brent Jackson 25 Mar 19
Replying to @jxnblk
And the theme specification has a new home, decoupled from the Styled System library! Feel free to comment on the open issue to keep the discussion moving forward
Reply Retweet Like
Brent Jackson 28 Jun 19
Replying to @jxnblk
Curious to hear others thoughts on this RFC for an optional "level 2" portion to the Theme Specification, which is meant to make theme objects themselves more portable:
Reply Retweet Like
Ian Storm Taylor 19 Mar 19
Replying to @jxnblk
Why is everything plural except for `space`, when using `spaces` would work just as well but eliminate the outlier?
Reply Retweet Like
Brent Jackson 19 Mar 19
Replying to @ianstormtaylor
Tech debt?? I haven’t changed that in styled system to avoid breaking changes. I’ve seen others use `spacing` for a key in the wild as well. To me the word "spaces" sounds like interior design whereas “space” implies visual design, e.g. negative space
Reply Retweet Like
kristo 🚲 18 Mar 19
Replying to @jxnblk
What do you think about having color intents like a material design palette so that you are tying components to intents not a specific color? I hate refactoring colors.tomatoRed to colors.fireRed
Reply Retweet Like
Brent Jackson 18 Mar 19
Replying to @jesus__kristo
This spec intentionally avoids color abstractions (because they are wildly complex) so your example *should* work – colors can be whatever shape you want
Reply Retweet Like
Darin Dimitroff 18 Mar 19
Replying to @jxnblk
Something I’m still unsure about is storing component variants in themes. Still find it more brittle compared to having a BaseButton component that I extend or something similar.
Reply Retweet Like
Brent Jackson 18 Mar 19
Replying to @deezel
Yeah I would be okay ditching that part of the general spec. It’s mostly documented now because Styled System supports it
Reply Retweet Like
Rob Gordon 18 Mar 19
Replying to @jxnblk
Different designs will call for different encodings of their tokens. Having a library of techniques to mix and match seems ideal. That said, the design system I’m working on now looks a lot like yours 😏
Reply Retweet Like
Brent Jackson 19 Mar 19
Replying to @rob__gordon
This isn’t a library and doesn’t dictate what file format to use. This could very well be written in json, yaml, toml, or whatever you want to use
Reply Retweet Like