Implementation Patterns

Block and rendering patterns are versioned, because they describe how a specific RHEA release builds and renders blocks. Everything else in this documentation — migration strategy, onboarding, security, operations, and governance — applies to all versions and is not duplicated per version.

Which version am I on?

A consuming site is pinned to a RHEA version by its code source, set centrally in the site's site.json (.code) in abbvie-migrated/eds-site-config — not by a committed fstab.yaml, which repoless sites do not have (see ADR-015). A self-contained file-based site pins it in its own fstab.yaml instead. Check whichever applies, then read the matching page below.

Version Status Patterns
RHEA 1.0 Current — powers all live consuming sites RHEA 1.0 Patterns
RHEA 2.0 In development RHEA 2.0 Patterns

What is versioned here

Topic Why it differs per version
Page loading phases Eager/lazy/delayed sequencing is tied to the release's scripts.js
Block resolution How EDS maps an authored block name to library code
Fragment system Which global components are fragment-loaded, and their caching behavior
Event bus The concrete event contract between blocks

What is not versioned

The repoless model, service stack, and environment topology are shared across versions — see Architecture Overview. Per-block implementation detail is not documented here at all; it lives in the README.md beside each block in the RHEA source repository.

On this page
h3
true