A design library is a collection of guidelines & standards that describe a design system and maybe template assets to go with it. Creating a library for an experience of any scale is no trivial matter. It’s not like you open up a code editor, chop things up, throw a ZIP file to some marketer and say “Here you go. Enjoy!” You’ve got to have a plan.
So, let’s assume you’ve done due diligence: your design system is stable and mature, and you’ve answered all the right questions to justify the effort. You are ready to get started.
What is the Process?
The process of creating a library involves many different activities across four sequential phases:
Analyze: understanding what it is, how it fits into your process, and what it’ll contain
Assemble: building it, including documentation, template assets, and how you’ll publish them
Adopt: communicating and getting everyone onboard
Adapt: administering & evolving it over time, through successive releases
Once you’ve broken down the plan into four chunks, it’s easier to zero conversation in on specifics: individual activities that may be obvious (documenting guidelines) and what’s not (oh, yeah, you’re right, I need a communications plan!).