Content Authoring Model

Executive Summary

RHEA content is authored in AEM Cloud Service via the Universal Editor (WYSIWYG), previewed via AEM Sidekick, and delivered through the Edge Delivery Services CDN. This page describes the operational content pipeline. For step-by-step, block-by-block authoring instructions, see the Authoring Guide in Confluence.

Content Pipeline

AEM Universal Editor          AEM Sidekick              Edge Delivery Services
──────────────────────        ────────────              ──────────────────────

Author creates/edits page
    |
    v
Content saved to AEM
    |
    ├── Preview ──────────────> aem.page (draft)
    |                           (instant, no publish needed)
    |
    └── Publish ──────────────> aem.live (production CDN)
                                (explicit publish action)

Authoring Environment

AEM Universal Editor

The primary authoring interface for RHEA content. Authors interact with a WYSIWYG editor that renders actual block output in real-time.

Feature Description
URL https://author-p50407-e476655.adobeaemcloud.com (prod); dev is author-p50407-e477588
Editor type Universal Editor (block-based WYSIWYG)
Block palette All RHEA blocks available via component models
Section editing Sections configured via section metadata
Inline editing Rich text fields editable directly on the page
Properties panel Block properties configurable via side panel

Component Models in the Editor

The Universal Editor reads component-models.json, component-definition.json, and component-filters.json to determine:

  • Which blocks are available for insertion
  • What properties each block exposes
  • Which blocks can be placed in which sections
  • Default values and validation rules

See the RHEA source repository (models/, component-*.json) for component model architecture details.

Page Structure

Every RHEA page follows this hierarchy:

Page
  ├── Head (head.html -- CSP, theme init, preloads)
  ├── Header (loaded from /nav fragment)
  ├── Main
  │     ├── Section 1 (Container/Column/Accordion/Carousel/Tabs)
  │     │     ├── Block A
  │     │     ├── Block B
  │     │     └── Section Metadata (background, width, spacing)
  │     ├── Section 2
  │     │     └── ...
  │     └── Section N
  ├── ISI (loaded from /isi/{variant} fragment, if enabled)
  └── Footer (loaded from /footer fragment)

Section Metadata

Authors configure section-level settings via a special metadata row at the end of each section:

Property Description
Background Color Section background from theme tokens
Width default / fullscreen / small / large
Content Width Inner content width constraint
Spacing Top and bottom padding
Gap Space between child blocks
Theme Section-level theme override

Content Fragments

Global components are authored as reusable content fragments. See EDS Architecture Overview — Fragment System for the complete fragment paths table and caching behavior.

Key fragments: Navigation (/nav), Footer (/footer), ISI (/isi/{variant}). Fragment loading uses Promise-based deduplication — if multiple components request the same fragment, only one network request is made.

Preview and Publish Workflow

AEM Sidekick

The AEM Sidekick browser extension provides the author's primary workflow controls:

Action Result URL
Preview View draft content (unpublished changes visible) https://{branch}--rhea--aa-pdcoe.aem.page/{path}
Publish Push content to production CDN https://main--rhea--aa-pdcoe.aem.live/{path}
Unpublish Revert live content to previous published version Previous version restored on aem.live
Edit Open page in AEM Universal Editor AEM author URL

These are the EDS origin URLs Sidekick itself operates on. When sharing a link, use the *.pdcoe.dev hostname instead — origins are being locked per environment, so a raw .aem.page link may return 401 for the recipient. See SEO and Crawler Hygiene.

Content States

State Visible On Description
Draft aem.page only Content saved but not published
Published aem.page + aem.live Content visible on production
Unpublished Neither Content reverted, not accessible
Preview (aem.page) always shows the latest saved content, regardless of publish state. Use preview to validate changes before publishing to live.

ISI Content Management

ISI (Important Safety Information) content requires legal review before publication. Always follow the pharma content review process.

Per-Page ISI Configuration

Each page can specify its ISI variant via page metadata:

Metadata Field Description
enableIsi true / false — whether ISI appears on this page (defaults to true if not specified)
isiPath Fragment path (e.g., /isi/isi-default, /isi/product-a)

The ISI block loads from the path specified in isiPath metadata, defaulting to /isi/isi-default. The ISI block checks multiple metadata name variations (camelCase, kebab-case, lowercase) for compatibility.

Query Index

EDS generates a query-index.json file that indexes all published pages. This index is used by:

Consumer Purpose
Search block Full-text search across site content
Breadcrumb block Resolve page titles from paths
Pagination block Navigate paginated result sets

The index includes page title, description, path, image, and last modified date.

On this page
h3
true