Delivering on Design Systems
Why a design system is more than a Sketch library
We’ve been working with a number of clients to create design systems. As part of these programs, we’ve also been developing component libraries to help drive adoption across our clients’ teams.
At this point, you’ve probably read and know all about the benefits of a design system. But the real trick is scaling a system within an organization, so that it can effectively support product development. In our experience, it’s not enough to just document a set of patterns and practices and hand over your sketch file.
One of the ways we help our partners adopt and scale their design is by helping them actually build the system. Developing a reusable library of components and providing reference implementation ensures product teams stay aligned and the experience stays consistent.
Beyond this, we also try to work with our clients to establish the process and practices necessary to sustain a system. The following posts from Edgar Rios and Max Wade share a few of our learnings scaling these systems.
Our collaborative workflow using Abstract
Edgar describes our most recent approach to applying a ‘Gitflow’ style of version control and peer review in Abstract.
How we deliver component libraries in React
Max offers a few best practices building and documenting reusable component libraries using Storybook and Jest.
If this article was helpful, please leave a few👏 to help us spread the word! Also, be sure to check out our other posts!
Find us on Facebook, Twitter, and Instagram or get in touch at thirteen23.com.
