styletron
braid-design-system
Our great sponsors
styletron | braid-design-system | |
---|---|---|
5 | 5 | |
3,321 | 1,468 | |
-0.1% | 0.7% | |
6.5 | 9.1 | |
3 months ago | about 16 hours ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
styletron
-
Tailwind CSS v3
Some technical thoughts as someone who could care less about fanboyism:
- One point where atomic CSS frameworks are supposed to shine over conventional CSS is bundle size, since they (at least the good ones) compile to only a single rule for any used value, rather than potentially repeating rules for semantically different classes.
- Another point where atomic CSS frameworks shine is just sheer volume of banging code out. When the bulk of your output is visual, mastering tools based on shorthands like tailwind, emmet, etc can feel very productive.
- Purely atomic CSS frameworks can make some workflows more difficult, e.g. by having too granular call sites and not allowing "let's see what happens to the overall theme if I do this design change" iterative style of work, or because workflows that edit CSS on the fly via browser devtools can no longer be used to limit impact within semantic lines (e.g. "I want to change padding only on buttons, without breaking everything else that happens to depend on the same padding value"). There are both design-oriented and debugging-oriented workflows that are affected in similar ways.
- You generally don't get visual regressions at a distance w/ atomic CSS. This matters at organizations where desire for pixel precision and simultaneously fickle design teams are the norm. But conversely, "can we just change the font size to be a bit bigger across the site" can often run into issues of missed spots. On a similar note, designs may become inconsistent across a site over time due to the hyper local nature of atomic CSS oriented development.
- Custom rules may as well be written in APL[0]; they usually aren't documented and it takes a "you-gotta-know-them-to-know-them" sort of familiarity to be able to work with them (or get back to them after a while).
- There are some tools that mix and match atomic CSS with other paradigms. For example, styletron[0] can output atomic CSS for the bundling benefits, but looks like React styled components from a devexp perspective, and has rendering modes that output traditional-looking debug classes for chrome devtool oriented workflows.
The main theme to be aware of: proponents rarely talk of maintenance, so beware of honeymoon effect. Detractors often omit that traditional CSS (especially at scale) also requires a lot of diligence to maintain. So think about maintenance and how AOP[1] vs hyperlocal development workflows interact with your organization's design culture.
[0] https://www.styletron.org/
[1] https://en.wikipedia.org/wiki/Aspect-oriented_programming
-
5 React.js UI Component libraries.
It is created, managed, and utilized by Uber. It includes a wide range of attractive components, with accessibility as the top focus. It is quick since it is built with the Styletron engine. Style overrides can be used to tweak themes, but in my experience, I've never required them because the design vibe they're trying for is precisely what I want.
-
Just-In-Time: The Next Generation of Tailwind CSS
[0] https://www.styletron.org/ [1] https://baseweb.design/blog/getting-started-with-styletron#getting-started-with-styletron
-
@blocz/react-responsive v3 is out
When we created the library, we were using styletron for our styles, and we wanted to bind the breakpoints we defined in @blocz/react-responsive with the breakpoints used for our styles.
braid-design-system
-
Feeling lost on grokking large libraries
I'm not trying to call a particular org or library out, because I think the ones I've been digging through (and prompted me to write this) are very high quality. It's vanilla-extract (a build-time CSS-in-JS library) and Braid Design System (built on vanilla-extract).
-
Recommendations for a really great Design System/Component Library?
Some of my favourites so far are.. https://seek-oss.github.io/braid-design-system/ https://carbondesignsystem.com/
-
5 React.js UI Component libraries.
Braid Design System
- 5 ways to manage layout space in React
-
Idea/Proof of Concept: Write UI like in Flutter or SwiftUI
Cool stuff! Iām doing something similar. My main inspiration was elm-ui and braid design system. With great keynote from its creator: from Reactive conf Get also inspired and good luck!
What are some alternatives?
styled-components - Visual primitives for the component age. Use the best bits of ES6 and CSS to style your apps without stress š
emotion - š©āš¤ CSS-in-JS library designed for high performance style composition
Fela - State-Driven Styling in JavaScript
Material UI - Ready-to-use foundational React components, free forever. It includes Material UI, which implements Google's Material Design.
Tailwind CSS - A utility-first CSS framework for rapid UI development.
linaria - Zero-runtime CSS in JS library
JSS - JSS is an authoring tool for CSS which uses JavaScript as a host language.
styled-system - ā¬¢ Style props for rapid UI development
React CSS Modules - Seamless mapping of class names to CSS modules inside of React components.
styled-jsx - Full CSS support for JSX without compromises
React Inline