Component-based design and development is here to stay and the most important tool to emerge from this paradigm is the component library. They provide many benefits, but they can also introduce friction. Fortunately, we can ease this friction with proper planning. Answering key questions before building a single component goes a long way towards ensuring the library's success.
Maui Jim recently faced a major software upgrade and redesign while expanding their international presence. They had ambitious performance goals and needed expert front-end development to achieve them. Chromatic delivered a successful component library and consulted on performance. The result: pages that load 2-4x faster.
Component libraries are living inventories of user interface elements (components). I hadn't yet built one for a client, but I'd heard of a few tools used to do so. What I didn't realize was just how many helpful tools there were. When deciding which to use, I realized I needed to define what I considered most important for this specific project. This post outlines that experience.
A couple of weeks ago, a client of ours needed a simple way to select some or all options in a multiple select form element that contained hundreds of options. They asked if there was a an easier way. jQuery to the rescue!