One Design System, Two Personalities: Building Shibolet's Community Hub

When I joined Shibolet & Co. as the solo product designer for their internal community hub, the engineering question landed fast: how do we keep ten flows consistent without a designer babysitting every screen? My answer was a Design System scoped to the real tension we were solving. The hub had to feel like a top legal practice and like a place people actually wanted to hang out. That meant tokens and components couldn't be neutral; they had to carry both registers. So I built two coordinated surface modes into the same system, one for the gravitas content like benefits, courses, and official notices, and one for the social layer like events, interest groups, and community activity. Same buttons, same spacing scale, same type ramp, different emphasis. For your R&D team, the payoff is predictability. Components encode the warmth-versus-seriousness decision so engineers aren't re-litigating tone in CSS. New flows compose from existing parts, reviews get faster, and visual drift stops creeping in across a four-month build. A Design System here wasn't decoration. It was the contract that let one designer and a dev team ship coherent work.