Evaluating Tools For Building a Component Library
At my day job we are going through the process of choosing a pattern/component library for the work that we do for our clients. What a lovely surprise to see a great write up this week on how someone else went about evaluating the right way to go.

As mentioned in On Building Component Libraries by Mark Perkins (another thought leader on this topic), “Integration is hard, so figure it out first.” I don’t want to pick a tool that adds too much complexity to the client’s existing workflow and infrastructure. I want to find the tool that provides the least amount of friction and provides value far into the future. Maybe even find the Holy Grail, where a website’s front end can use the same CSS, JS, and/or template files as the library.
An excerpt from Evaluating Tools For Building a Component Library