Designsystemet

Base Architecture: Designsystemet (Digdir) & Drupal Single Directory Components (SDC)
Target Audience: Norwegian public sector municipalities, government agencies, and vendors building on Drupal.

Vision & Core Concept
An enterprise-grade starter theme for Norwegian public sector websites, built directly on Designsystemet. The theme bridges Drupal’s site-building capabilities with Norway’s unified public design standard, aiming to streamline municipal site creation, enforce universal accessibility, and dramatically reduce frontend development overhead.

Technical Evolution & Roadmap

Phase 1: Foundation (Current)
└── Simple wrapper theme loading core Designsystemet assets.
└── Governance handled directly by primary maintainers.

Phase 2: SDC & Low-Code Expansion (In Progress)
└── Conversion of Designsystemet components into native Drupal Single Directory Components (SDC).
└── Automated design token synchronization pipeline (Figma / npm → Drupal CSS variables).
└── Low-code site building via block and paragraph configurations.

Phase 3: Ecosystem Integration & Open Governance (Future)
└── Full compatibility with the UI Suite ecosystem (UI Patterns 2.x, UI Styles).
└── Expansion from primary maintainers to an open public-sector working group.

Core Features & Standards
Native SDC Architecture: All component patterns are encapsulated as Drupal Single Directory Components, ensuring modern, modular, and maintainable frontend code.
Low-Code / No-Code Vision: Allows site builders to assemble pages using pre-built SDC patterns without writing custom HTML or CSS.
- Future-Proof Token Sync: Planned automated pipeline to pull JSON design tokens from Designsystemet directly into Drupal, keeping styling automatically aligned with national design updates.
 Compliance & Public Sector Standards: Tailored to adhere to Digdir guidelines, Norwegian WCAG requirements, GDPR, and privacy best practices out of the box.

Project Roadmap Checklist
- Component Library | Map Digdir core primitives (Buttons, Cards, Accordions, Alert Boxes) directly to SDC folders (components/[name]).
- Data Integrity | Standardize component schema definitions (*.component.yml) to ensure seamless future integration with UI Patterns 2.x.
- Token Pipeline | Define the build toolchain (e.g., Style Dictionary or PostCSS) for processing Designsystemet tokens into CSS custom properties.
- Community | Establish clear maintainer guidelines and set up a public issue queue before transitioning to a multi-agency working group. (edited)