EDS Architecture Overview
Executive Summary
RHEA is a centralized AEM Edge Delivery Services block library that follows a repoless architecture, enabling multiple sites to share a single codebase for blocks, scripts, and styles without code duplication. The library is built on the aem-boilerplate foundation and integrates with AEM Cloud Service for content authoring via the Universal Editor.
This page covers the parts of the architecture that are stable across RHEA versions — the service stack, the repoless model, and the environment topology. The block and rendering patterns that differ between RHEA 1.0 and 2.0 live in Implementation Patterns.
Solution and Service Stack
When to Use RHEA
| Criteria | RHEA (EDS) | Traditional AEM Sites | Static Site |
|---|---|---|---|
| Content-driven pages | Yes | Yes | Partial |
| Lighthouse 100 performance targets | Yes | No | Yes |
| WYSIWYG authoring (Universal Editor) | Yes | Yes | No |
| Reusable blocks across multiple sites | Yes (repoless) | Partial (content fragments) | No |
| Pharma-specific components (ISI) | Yes | Custom build | Custom build |
| Real-time preview/publish | Yes (Sidekick) | Yes (workflow) | CI/CD only |
Service Stack
| Layer | Service | Purpose |
|---|---|---|
| CDN / Edge | AEM Edge Delivery (aem.live / aem.page) | Global content delivery, edge-side includes, preview/live separation |
| Content Authoring | AEM Cloud Service (Universal Editor) | WYSIWYG block-based authoring with component models |
| Content Source | AEM Author, one per environment (see Environments) | Content repository, asset management, fragment storage |
| Block Library | RHEA - Reusable High-Efficiency Edge Architecture using AEM EDS | Reusable blocks, shared scripts, utility library |
| Build Pipeline | GitHub Actions + Husky pre-commit hooks | SCSS compilation, linting, JSON model merging |
| Design Tokens | Style Dictionary + custom transforms | Figma-to-CSS token pipeline with three-tier hierarchy |
| Styling | SCSS + PostCSS (Autoprefixer) | Compiled to .min.css, auto-imported mixins |
| Analytics | Adobe RUM + custom data layer | sampleRUM() for Helix analytics, window.dataLayer.events for custom tracking |
| Sanitization | sanitize.js + DOMPurify | XSS prevention for authored and fetched content — two sanitizers at different points |
| Event System | mitt (vendored scripts/vendor/mitt.min.js) | window.Bus inter-component event emitter |
Repoless Architecture
How it works:
- RHEA is a standalone GitHub repository containing all block definitions, scripts, styles, and component models.
- Consuming EDS sites point at RHEA as their block source through the AEM Configuration Service API, not a committed fstab.yaml — see ADR-015.
- When a page is requested, EDS resolves block references through the RHEA repository.
- Each consuming site can override individual blocks by placing a same-named block in their own repository.
- Global components (header, footer, ISI, breadcrumb) are loaded from per-site content fragments.
Benefits:
- Single source of truth for block code and behavior
- Bug fixes and enhancements propagate to all consuming sites
- Consistent design language enforced via shared design tokens
- Reduced maintenance overhead across the portfolio
Environments
The rhea family runs three Cloudflare-fronted environments. Each is served through a custom *.pdcoe.dev hostname (via a Cloudflare routing worker) that fronts the underlying EDS origin. Hostnames, branches, and CDN config are managed in abbvie-migrated/eds-site-config (sites/rhea/envs/<env>/env.yaml).
| Env | EDS site | Branch | Live | Preview | AEM Author |
|---|---|---|---|---|---|
| Prod | rhea | main | rhea.pdcoe.dev | rhea-preview.pdcoe.dev | author-p48761-e275513 |
| Stage | rhea-stage | stage | rhea-stage.pdcoe.dev | rhea-stage-preview.pdcoe.dev | author-p50407-e476656 |
| Dev | rhea-dev | develop | rhea-dev.pdcoe.dev | rhea-dev-preview.pdcoe.dev | author-p50407-e477588 |
A fourth env, sandbox-dev, exists on the develop branch against a sandbox AEM program and is not Cloudflare-fronted.
Each *.pdcoe.dev hostname is a proxied CNAME onto an EDS origin, routed by a per-env Cloudflare worker. The hostname-to-origin mapping, the worker names and the DNS requirements are documented once, in Environment Access Control — deliberately not repeated here, because it was previously stated in four places and drifted.
Branch-specific previews follow the pattern https://{branch}--{eds-site}--aa-pdcoe.aem.page/ (or via the routing worker's ?ref={branch} on the preview hostname). Branch names are constrained to 63 characters due to DNS subdomain limits.
Environments follow the naming convention {project}-{environment} (e.g. rhea-stage, rhea-dev), except for prod, which reserves the bare rhea name.
Implementation Patterns
Page loading phases, block resolution, the fragment system, and the event bus are version-specific — they describe how a particular RHEA release renders blocks.
Related Documents
- Implementation Patterns — Version-specific block and rendering patterns
- Code-level docs (block library, design tokens, component models) live in the RHEA source repo itself — see its README.md, style-tokens/README.md and models/README.md
- DevOps Overview — Build and delivery pipeline at a glance
- Governance — Architecture Decisions — Rationale behind key choices