
Overview
The problem with a PDF
What is in it
Two brands, one system
brand/primary, brand/alert and bg/page resolve differently depending on the active theme, and a single CSS class switch re-skins the entire component library from BDA navy to SIPY green. The components do not know which brand they are rendering. That is the point: a sub-brand is a set of values, not a fork of the code.
The hard part: shipping into a legacy CMS
Keeping Figma in step
Technologies used
- Frontend: React 19, TypeScript, Vite, React Router, Tailwind CSS v4.
- Motion and icons: Framer Motion for component transitions, Lucide for iconography.
- Export pipeline: a Node script that generates inline-styled HTML snippets per card variant for DNN.
- Design bridge: a Figma plugin plus a written variable-mapping spec, code to Figma.
- Lead capture: a separate standalone app for the credit-application lead form.
