Multi-Brand Knight

The Paladin Design System was created to defeat the multi-headed monster that is multiple brands built with one design system. This system was designed to be vigilant and scale in the event that more brands cropped up.

Role Building Components, Updating Variables, Creating New Brand Templates
Collaborators Jason Grotian, Claire Squire, Jean Kwon
Tool’s Token Studios, Figma
Cross-Functional Partners SVOD, AVOD, Brand Stakeholders, and Developers

paladin-design-systems-ds-project-img-1x25.jpg

The Squire - Beginnings

The design system was in whole a white label system that had interchangeable themes. These were mostly created using a neutral scale and based off of brand guidelines. Initially I helped by creating these themes for several brands that needed them. That’s where I learned how each token was utilized and what the value of those tokens represented. The system worked exceptionally well when swapping themes between each of the brands making designing for multiple brands simple. All you had to do was design within the Paladin system and duplicate and swap themes in order to showcase a different brand theme.

The coolest part of this system was that it comprised of only 50 different tokens making it easy to scale if more brands needed onboarding or new feature growth. Jason my VP of Design came up with this system. I learned a ton from him by diving into the theme templates for new brands.

paladin-primary-theme-template-1x25.jpg

White label theme template for building different brands with the Paladin Design system.

The Blacksmith’s Sword - Component Exploration

Once I was well acquainted with the system, I would help our Systems Designer/Maintainer Claire out with building and contributing to the system. If I had downtime I’d reach out to her and ask if there was anything I could take off her plate. She was our only systems designer and had 5 people feeding her new components and features. I knew a baseline for component building and enjoyed doing that. She would give me components to build out or documentation to write up. I’d always have her review and merge the changes I gave and usually there was little to no feedback. Which is a reflection on her component building and teaching.

paladin component build1x25.jpg

Spotlight Desktop Component Build with Props - A Component that I designed

Knight-Errant