Knapsack provides a consolidated platform to manage design and code decisions across your product and brand ecosystem enabling you to deliver better experiences to market, faster.
.png)
.png)
.png)
.png)
I feel its a great product. It will not be possible to have a design system like this with just myself without Knapsack because it really enables me to do the work of two or three people or even more of the design system maintenance…It would be a big setback if we lose you.
The token structure is something we’ve been leveraging a lot, especially as we scale. It’s flexible enough for us to manage different brand guidelines within the same system, which is crucial for our team.
We’ve been experimenting with the token structure in Knapsack, and it’s been really helpful for maintaining consistency across our design system. The way Knapsack handles tokens makes it easier to implement changes across the board.
Knapsack is a much easier platform to manage than our previous homegrown design system. Especially around documentation. There’s also lots of promise around token management.
Tokens are a key part of our workflow, and Knapsack’s approach has streamlined the way we manage and apply them across our design system. It’s made things more consistent and easier to update.
Knapsack gives us prototyping in code that designers can play with. And, dropping our technical scope of maintaining the code and Storybook is way more valuable to us than trying to maintain those things with the hope that eventually it becomes a design asset.
Knapsack’s approach simply matches how we expect collaboration software to work—log in, make changes, and trust that everyone sees what you did. Members of our team trust that everything in our design system is up to date and official.
Knapsack can be a great accelerator, helping organizations to provide that platform. We've successfully partnered with Knapsack when building design systems with our clients, and it's always part of our consideration on the best solutions to recommend.
Knapsack has become an integral and central part of our production process for both front-end developers and product owners...and it keeps getting better.
Once we moved to Knapsack the versioning was key. That was a big selling point to be able to have automatic versioning, so then any dependant will know exactly what version they are getting and you don't have to structure releases. Structuring a release manually can be really valuable for some projects but like you said the change was happening at such a fast pace that we needed a way to automate that.
