657: David Darnes on Web Components and Design Systems

What It Covers

David Darnes discusses building Nord Health's design system using web components, achieving framework-agnostic consistency across decade-old monoliths and modern Nuxt applications while maintaining design-development parity through public documentation and progressive enhancement strategies.

Key Questions Answered

• •Framework-Agnostic Architecture: Nord Health's web component design system runs identically on decade-old monolith stacks and modern Nuxt applications without code changes, proving web components enable stack migrations without forcing design system rewrites. Components update via package.json version bumps alone, delivering features intravenously across different technology stacks simultaneously.
• •Public Documentation Strategy: Making design system documentation publicly searchable serves dual purposes: internal teams find components through Google searches, and external developers evaluate company quality through visible design standards. This approach successfully recruited team members who discovered the system online and wanted to contribute to high-quality component libraries.
• •Progressive Enhancement Pattern: Building web components without mandatory Shadow DOM enables markup-forward approaches where developers control templates through slots and data attributes. This strategy allows components to function as HTML enhancements rather than JavaScript requirements, supporting graceful degradation when scripts fail while maintaining customization flexibility through standard templating languages.
• •CSS Custom Property Optimization: Declaring CSS variables inside components enables state changes through single property updates rather than rewriting multiple declarations. Hover and focus states change one custom property that cascades to background, border, and box-shadow simultaneously, reducing error-prone repetitive CSS and simplifying maintenance across component variants.
• •Token System Layering: Multi-layer token architectures with product-specific overrides, defaults, and legacy compatibility layers require designer-developer alignment. Figma variable systems using immutable IDs enable name changes without breaking references, while CSS variable renames break everything. This fundamental difference demands careful synchronization strategies between design tools and production code.