Components at Scale: Build a Library That Scales
Help your team with components that stay sane as you grow
So you want to build a component library — nice! The fact that you have even checked out this piece indicates that you’re working on a platform that's scaling. Or perhaps you’ve just hired some new devs and realized your codebase is diverging at a rate faster than quality checks can keep up with, while developers are introducing too many multiple ways of solving the same problem, increasing your technical debt.
A component library can help your developers and designers work in a much more consistent way, making efficient use of time when executed correctly.
There are always multiple ways of solving a problem, though, and you may find yourself in a situation where you may use different tools to what we use here. The architecture and tools we discuss here are to suit the particular challenges facing our team. Your situation and requirements may well be different. Thankfully, we have a wealth of options to pick from, and I would urge you to do your own research as well.
Without further ado, let's have a look at the key tech we want to incorporate.
