I think one thing to call out with design systems is that while they’re typically not the source for innovation, it should support teams experimenting with new UI ideas by providing low-level “nuts and bolts” to help experimental UI at least stay cohesive with the system: design tokens, CSS parts in components, constructable style sheets, etc
“What’s in a design system figma library isn’t as much of a spec for developers to build it out. What this figma library is is a promise of what is in code. It is a representation of what exists in the coded design system.” Perfect
How do you maintain consistency with the versions of components published? i.e. how do apps know of the latest published version of the component without manually changing the version in packgejson and hitting install?
I appreciate the take here to try an establish a definition for what constitutes a 'design system'. I think I would interpret it even more generically: A design system is in essence a governance mechanism which describes how some scope of products are communicated to its audience. Design systems are documented to provide the guidance. Many find this most convenient to document within Figma, given how valuable it can be to express that guidance through visualizations. Figma/Sketch/XD and similar apps typically build out features to help design teams keep a consistent reference of these concepts that can be instantiated to make a design team's workflow more flexible and resilient to change. Similarly, a component library is just a tool to help templatize the expression of that system in a manner where that communication medium is in some digitally interactive format (web/native apps). Ultimately, the implementation of the system is a challenge that a team or organization will have to figure out how to best maintain and scale.
Syntax 800 episodes?? Since when?! Congratulations!!
I think one thing to call out with design systems is that while they’re typically not the source for innovation, it should support teams experimenting with new UI ideas by providing low-level “nuts and bolts” to help experimental UI at least stay cohesive with the system: design tokens, CSS parts in components, constructable style sheets, etc
“What’s in a design system figma library isn’t as much of a spec for developers to build it out. What this figma library is is a promise of what is in code. It is a representation of what exists in the coded design system.” Perfect
How do you maintain consistency with the versions of components published? i.e. how do apps know of the latest published version of the component without manually changing the version in packgejson and hitting install?
I use npm-check-updates to see what needs to be updated
First☺️
I learned a lot from this episode. Loved Brad's Sick Pick. I am going to print out that quote and paste it in my office.
I appreciate the take here to try an establish a definition for what constitutes a 'design system'. I think I would interpret it even more generically:
A design system is in essence a governance mechanism which describes how some scope of products are communicated to its audience.
Design systems are documented to provide the guidance. Many find this most convenient to document within Figma, given how valuable it can be to express that guidance through visualizations.
Figma/Sketch/XD and similar apps typically build out features to help design teams keep a consistent reference of these concepts that can be instantiated to make a design team's workflow more flexible and resilient to change.
Similarly, a component library is just a tool to help templatize the expression of that system in a manner where that communication medium is in some digitally interactive format (web/native apps).
Ultimately, the implementation of the system is a challenge that a team or organization will have to figure out how to best maintain and scale.
confused.
Second!
Really just here for the Michigan hockey hat. Go Blue!
Go Blue!
CHEATERS!!