j
u
l
z
d
e
s
i
g
n
Design System Library
Objective
Prudential Global Theme and Design System Website were a great success and I took advantage of this momentum to propose building a dedicated team and treat Design System as a product.
Process
Prudential Global Theme and Design System Website were a great success and I took advantage of this momentum to propose building a dedicated team and treat Design System as a product.
We began by conducting an audit of existing components and patterns finding any redundant combinations and merge duplicates.
In order for the library to succeed we ensured developers had a great experience. To accomplish this, we determined what made a successful library by conducting several developer interviews and competitive analysis.
Attributes of a great library are detailed documentation, concise release notes, changelogs, consistency, ease of use and open source frame of mind.
Using Codepen integrated with our theme and SASS variables we conducted smoke tests for modularity, accessibility, and responsiveness.
We focused on build quality, not quantity, we took time to thoroughly test and document. Often functional accessibility was the most complicated and time-consuming process, sometimes going way past sprint deadlines.
The team Automation Engineer implemented full integration into the CI/CD pipeline. Some highlights were:
Docker-based container first development.
Full integration with CI/CD pipeline.
80% Code coverage.
Supplemental auto generated documentation via Compodoc.
One of the most prominent team goals I set was to change existing siloed culture by introducing a collaborative workflow, promoting the benefits of a global library, conducting workshops, and general pair programming.
Evangelized a collaborative workflow.
Conducted workshops in New Jersey, California, and Ireland.
Fostered culture of collaboration by conducting regular workshops and facilitated bi-weekly public forums.
