What This System Protects
The design system is a product surface, not just internal documentation. It gives stakeholders a shared place to review decisions and gives developers a source of truth for implementation.
Foundations
Brand principles, typography, color, spacing, accessibility, and SEO/AI-readiness rules.
Review Foundations →Components
Visual examples of the reusable UI components implemented in the Next site.
Review Components →Templates
Page templates and section patterns that keep content editable without allowing layout drift.
Review Templates →Decision Flow
Changes should move from documented intent to tokens and components, then into templates and rendered pages.
- Update the published design-system page that describes the decision.
- Reflect the decision in design tokens or reusable components.
- Apply the component or token change through templates.
- Keep page content editable through structured fields, not custom layout controls.
Editor-Safe Publishing Model
Editors Can Manage
- Page titles, summaries, and hero copy.
- Cards, proof points, FAQs, relationships, and CTA copy.
- SEO title and meta description fields.
- Service, industry, location, and insight relationships.
The System Controls
- Template structure and component selection.
- Heading hierarchy and semantic HTML.
- Design tokens, spacing, color, and typography.
- JSON-LD, metadata, and internal-linking rules.
Supporting Markdown docs remain available in Foundations, but the review surface should be these published pages.