Another example of how Knapsack helps teams go from design to code quickly and efficiently to deliver real value to the product teams that use your design system. So many folks are focused on documentation being the way to connect design and code (and docs do matter), but having a structured, codified, version controlled way to specifically define how you connect Figma to a coded component is really what helps us deliver value to product teams that use the design system.
"I think we need to get us back in the business of designing and less of maintaining design systems." This stuck with me from a recent conversation with a design system leader at a F500 company. "We create the thing on the left (Figma) and then create the thing on the right (code)...but then we’re not always aligned. So we try to create this thing in the middle (documentation)...that part in the middle becomes its own job and its own time suck." Sound familiar to anyone? We waste so much time right now just managing 'the thing in the middle' as he called it - the thing we make to try to help our teams understand and manage the gap between design (Figma components) and code (coded components). But what if this part just went away? What if all you had to do was connect your design and code libraries to instantly build docs and create clarity around where teams are aligned and not? What if everyone working on a project could get their expectations aligned, even if their design and code isn't (yet)? Knapsack is making it easy for teams to manage and align their design and code systems at any scale. Coming soon to a Knapsack workspace near you... #designsystems #digitalproduction #productpreview #sneakpeek
