If you've spent years building structured, component-driven sites in  Drupal , you've developed strong instincts about how a design system should work. Components have templates, stylesheets, and defined data points. Editors fill in fields. The system enforces consistency. It's a model that scales well for universities, government agencies, and large organizations—the kind of projects we've focused on for most of our history at Lullabot. WordPress and  Gutenberg have fundamentally different philosophies on how editors and components interact. Understanding that difference is the key to building a design system that actually works in this ecosystem. Starting from different places In Drupal, the standard approach is to start with a minimal base theme—something with just enough scaffolding to build on—and then layer in exactly what the project needs. It's a bottom-up model that gives teams a lot of control. Our WordPress project took the opposite approach.…