Implementation Patterns — RHEA 2.0
In development
RHEA 2.0 is not yet released and no consuming site runs it. These patterns are being defined — sections below are placeholders until the corresponding decision is made. Treat RHEA 1.0 Patterns as authoritative for anything currently in production.
Page Loading Architecture
Not yet documented. Record the 2.0 loading phases here once the rendering approach is settled. If a phase is unchanged from 1.0, say so explicitly and link to the 1.0 section rather than copying the table — that keeps the delta obvious to readers.
Key Architectural Patterns
Block Resolution
Not yet documented. Covers how EDS maps an authored block name to library code in 2.0.
Fragment System
Not yet documented. Covers which global components are fragment-loaded and their caching behavior in 2.0.
Event Bus
Not yet documented. Covers the concrete event contract between blocks in 2.0.
Changes from RHEA 1.0
| Area | 1.0 | 2.0 | Status |
|---|---|---|---|
| Page loading | Three-phase eager/lazy/delayed | — | Not decided |
| Block resolution | Directory match on block name | — | Not decided |
| Fragment system | Promise-deduplicated fragment fetch | — | Not decided |
| Event bus | window.Bus via vendored mitt | — | Not decided |
Related Documents
- Architecture Overview — Service stack, repoless model, and environments (all versions)
- RHEA 1.0 Patterns — Current production patterns
- Development — Code-level docs (block library, design tokens, component models) in the RHEA source repo
- Governance — Architecture Decisions — Rationale behind key choices
On this page
h3
true