Consuming Site Guide

Executive Summary

RHEA uses the EDS repoless architecture to share blocks across multiple sites. Consuming sites reference RHEA as their block source and can selectively override individual blocks by placing same-named blocks in their own repository.

How Repoless Works

In a traditional EDS setup, each site has its own block code. With repoless, consuming sites delegate block resolution to RHEA:

Page request → EDS CDN → Check consuming site repo for block
                           ↓ (not found)
                         Check RHEA repo for block
                           ↓ (found)
                         Serve block JS/CSS from RHEA

If a consuming site has a block with the same name as a RHEA block, the consuming site's version takes precedence (local override).

Two consumption models

There are two ways a site can consume RHEA:

  1. Repoless via eds-site-config (primary at AbbVie) — the site has no code repo of its own. Code source and path mappings are set centrally in the site's site.json (.code, .public.paths) managed in abbvie-migrated/eds-site-config. There is no per-site fstab.yaml / paths.json / helix-config.yaml.
  2. Self-contained / file-based — the site has its own EDS repo with local fstab.yaml, paths.json, and optional block overrides. The steps below describe this model; the RHEA source repo's file-based-starter/ provides templates.

Use the repoless model for standard AbbVie sites; use the file-based model only when a site genuinely needs its own repository.

Setting Up a Consuming Site (file-based model)

1. Repository Structure

Create a new EDS repository with at minimum:

my-site/
  fstab.yaml              # Content source configuration
  head.html               # Can extend RHEA's head.html
  paths.json              # Block resolution paths (points to RHEA)
  blocks/                  # Local overrides only (optional)
  styles/                  # Site-specific style overrides (optional)

2. Configure fstab.yaml

Point to your AEM content source:

mountpoints:
  /: https://author-p{programId}-e{envId}.adobeaemcloud.com/content/{site}/

3. Configure paths.json

Map block resolution to RHEA:

{
  "mappings": [
    "/blocks/:path*",
    "/scripts/:path*",
    "/styles/:path*"
  ]
}

This tells EDS to resolve blocks, scripts, and styles from the RHEA repository when not found locally.

4. Configure the code source

Set the code source to RHEA via the EDS Admin API SiteConfig (.code), using the config-as-code flow in eds-site-config or the Admin UI:

  • Code repository: abbvie-migrated/rhea
  • Content repository: Your site's content repo or AEM instance
helix-config.yaml is not a current mechanism. Code source is configured through the Admin API SiteConfig (site.json), not a per-repo helix config file.

Overriding a Block

To customize a RHEA block for your site, place a same-named block in your local blocks/ directory:

my-site/
  blocks/
    header/
      header.js        # Your custom header
      header.scss
      header.min.css

EDS will use your local header instead of RHEA's. All other blocks continue to resolve from RHEA.

Override Best Practices

  • Copy, don't modify — start by copying the RHEA block and modifying it
  • Keep the same API — maintain the same component model fields so authored content remains compatible
  • Document overrides — note which blocks are overridden and why in your site README
  • Pin to a RHEA version — consider using a specific RHEA branch/tag for stability

Global Components

Header, footer, ISI, and breadcrumb are loaded from content fragments. See EDS Architecture Overview — Fragment System for the complete fragment paths table.

Each consuming site provides its own fragment content at the standard paths (/nav, /footer, /isi/{variant}). The block code comes from RHEA; the content comes from each site's AEM instance.

Design Token Inheritance

Consuming sites inherit RHEA's design token values via the compiled CSS custom properties. To customize tokens:

  1. Override specific CSS custom properties in your site's styles/ directory
  2. Or provide a custom figma-tokens.json and run the RHEA build pipeline locally
Token overrides at the consuming site level are a CSS-only concern. The token pipeline (Style Dictionary) runs only in the RHEA repository.

Testing a Consuming Site

  1. Run aem up in your consuming site repository
  2. Verify blocks resolve from RHEA (check Network tab for block JS/CSS origins)
  3. Test any local overrides render correctly
  4. Verify fragment content loads (header, footer, ISI)
  5. Test across viewports and themes
On this page
h3
true