Operations

Two jobs live here, and they want different pages. Standing a site up is a sequence that crosses AEM, GitHub and Cloudflare, with ordering constraints that are not obvious from any one of them. Keeping one running is escalation paths, monitoring and the test suite that gates every change.
Onboarding Guide
The five phases from intake to handoff, with who owns each step and the week estimates. Start here for a new consuming site.
true
true
card-gap-default
/content/rhea/operations/onboarding
{"operationsCardClick": true}
Site Provisioning
The provisioning chain across AEM, GitHub and Cloudflare — including the two ServiceNow requests nobody on the delivery team can self-serve, and the ordering that makes a first deploy fail if taken out of sequence.
true
false
card-gap-default
/content/rhea/operations/site-provisioning
{"operationsCardClick": true}
Consuming Site Guide
How a site consumes the block library: the repoless model, how block resolution falls back to RHEA, and how to override a single block without forking.
true
false
card-gap-default
/content/rhea/operations/consuming-site
{"operationsCardClick": true}
Content Authoring Model
The operational content pipeline — Universal Editor to Sidekick to CDN, page structure, fragments, and the preview-versus-published states.
true
false
card-gap-default
/content/rhea/operations/content-model
{"operationsCardClick": true}
Support and Incident Response
Four support tiers with explicit escalation paths, severity classification and response targets, plus where each kind of log actually goes.
true
false
card-gap-default
/content/rhea/operations/support
{"operationsCardClick": true}
Quality Assurance
The 204 automated tests every change is verified by, what they do and do not cover, and how a brand repository inherits and extends them.
true
false
card-gap-default
/content/rhea/operations/quality-assurance
{"operationsCardClick": true}