Design Principles
Executive Summary
The standing principles every RHEA architecture decision is evaluated against. Where an Architecture Decision Record captures a single choice and the tradeoffs accepted at the time, these principles are the criteria those choices are judged by — they are not themselves decisions, and they do not carry a status or a date.
Performance First
Every architectural decision is evaluated against Lighthouse 100 targets. Performance is a feature, not an afterthought.
Shared by Default, Override When Needed
The repoless model shares everything by default. Individual sites override only the blocks they need to customize.
Content Author Autonomy
Authors should be able to accomplish their work without developer intervention. Block configuration, section metadata, and fragment management are author-controlled.
Progressive Enhancement
Pages are functional with HTML and CSS alone. JavaScript enhances interactivity but is not required for content consumption.
Accessibility as a Requirement
WAI-ARIA patterns, keyboard navigation, focus management, and semantic HTML are requirements, not optional enhancements.
Related Documents
- Architecture Decisions — the 15 records these principles are applied to.
- EDS Architecture Overview — the solution stack the principles shaped.
- Security Model — where the accessibility and progressive-enhancement principles meet the CSP and sanitization rules.