The problem
A Swoogo microsite ships with a serviceable default look. This client’s brand team had their own reference designs — logo usage rules, a defined color palette, specific typography — and none of it was showing up on the event site their registrants actually saw. The microsite worked. It just didn’t look like them.
The approach / solution
- Took the client’s brand reference materials as the source of truth: logo treatment, color rules, typography.
- Defined a full set of design tokens from those references: color values, a type scale, spacing.
- Compiled a production stylesheet from those tokens and applied it across the account’s Swoogo theme.
- Built the entire system inside Swoogo’s native Twig templating and theme layers, since that’s the only route a Swoogo page builder supports.
Outcome / result
The microsite now reads as the client’s own site: their colors, their type, their spacing, consistently across every page a registrant touches. It’s one of two complete design-system builds we’ve done at this depth across all our Swoogo theme work.
Why it matters for enterprise event-tech
Conference and association brands invest real budget in how they look everywhere else — print, their main website, their app. A registration microsite that doesn’t match undercuts that work at the exact moment a registrant is deciding whether the event feels credible. Full token-level theming is what closes that gap; a swapped logo and a header color don’t.
