Adovo

AEM Sites Playbook: Strategy, Delivery and Operations

A 20-part AEM Sites guide for business owners, decision makers and practitioners, with community cases, decisions, worked examples and worksheets.

November 10, 2026

Strategy, Delivery and Operations

AEM Sites succeeds when people can create the right content, approve it, deliver it to the intended audience and keep the service useful as requirements change. That requires agreements between content teams, designers, engineers, analysts and platform owners. A page that renders correctly answers only one part of that problem.

The playbook consists of twenty independent chapter pages, connected by this index and shared worksheets. It covers platform selection, implementation, authoring, governance, delivery, experience quality, operations and migration. Start with the decision or task you need; chapter numbers provide a suggested sequence rather than a prerequisite to read everything. The decisions and tests apply to the environment you actually operate; they are not a recommendation to adopt every AEM capability.

Choose a reading path

Scroll horizontally if needed.

Choose a reading path: table 3
ReaderStart hereBring to the discussion
Business owners in marketing, product, content and regional teamsChapters 1–2, the decisions in 4 and 6–10, experience outcomes in 13–17, and the readiness decision in 20Customer tasks, content ownership, deadlines, acceptable limitations and success measures
Decision makers responsible for architecture, investment or the platformChapters 1–3, 5–8, 11–14 and 18–20Constraints, alternatives, operating costs, dependencies, accountability and change authority
Practitioners who author, approve, design, develop, test, administer or analyzeEnter through the task index, then follow the relevant chapters and worksheetsActual versions, representative content, reproducible observations and recovery evidence

Business owners should leave each chapter knowing what to decide and what evidence to request. Practitioners should leave with an action they can perform and a way to judge its result. The platform owner keeps those decisions connected so a local repair does not create a problem for another team.

Establish your deployment context

Record the AEM release and service pack, hosting arrangement, editor, Core Component versions, custom extensions, runtime, delivery path and connected systems before following a procedure. AEM 6.5, AEM 6.5 LTS and AEM as a Cloud Service have different compatibility and operating requirements. AMS describes a managed hosting context. Edge Delivery Services is a delivery approach with distinct authoring choices. It is not another 6.5 service pack. Check the LTS guidance, component compatibility table and Edge Delivery overview for the relevant branch.

Four clearly hypothetical examples recur: a localized campaign launch, a product-data import consumed by another channel, a platform upgrade and recovery after accidental deletion. They illustrate decisions and tests. They are not combined community incidents or Adovo customer results.

Use the working records

Open the companion worksheets with the chapter you are using. Give each decision, change and exception an owner and review date. Keep actual credentials, personal data and sensitive logs in approved internal systems; record a restricted evidence location rather than copying them into a shared workbook.

Community discussions provide the examples and highlight questions to investigate. Specific examples link to the original discussion through short descriptive phrases. Version context is included where it changes the action. Adobe documentation establishes product boundaries; organizational requirements determine acceptance. A participant's reported repair can suggest a useful test without becoming a universal configuration recipe. The evidence page explains the research scope, limits and official documentation.

Chapter summaries and links

Decide and organize

1. Strategy, value, ownership and adoption

What outcome justifies the work, and who will operate it? An outcome, ownership and adoption brief with explicit investment assumptions.

2. Platform, hosting and experience architecture

Which platform, authoring and delivery choices fit the requirements? A tested architecture decision and responsibility map.

Build the content platform

3. Engineering foundations and maintainable customization

How should the application be extended and diagnosed? A maintainable customization/dependency inventory and request-level tests.

4. Authoring, components, templates and design systems

Can authors create the intended experience with the supported components? A component/template catalog and representative authoring acceptance evidence.

5. Structured content, fragments and headless delivery

How should structured content be modeled, managed and consumed? A content-model, ownership and consumer contract with reference/change tests.

6. Multisite, localization and local ownership

What remains central, what can vary locally and how do translations stay correct? A brand/locale ownership map and repeatable rollout/translation checks.

Govern and publish

7. Governance, workflows, approvals and content lifecycle

What does approval mean, and how is content corrected or retired? An owned lifecycle, meaningful comparison baseline and tested workflow.

8. Identity, permissions, security and privacy

Who may perform each action, and how is that authority enforced? A capability/data-exposure matrix with allowed and denied test results.

9. Assets, media and Sites dependencies

Are media, references and delivery behavior ready for the experience? An asset dependency/delivery record with processing, rendition and withdrawal checks.

10. Preview, publication, scheduling and withdrawal

How do we release and remove the complete approved experience? A publication record connecting approval, dependencies, scheduling and public observation.

Deliver and improve the experience

11. Delivery, Dispatcher, CDN, domains and caching

Which layer controls the request, redirect or stale response? A route/cache policy and request-level evidence through the actual delivery path.

12. Performance, queries and capacity

What is slow, what causes it and does the proposed change help? A repeatable performance baseline, diagnostic packet and regression comparison.

13. Site search, relevance and content discovery

Can customers find the right results in the right locale and access context? A search acceptance collection covering relevance, exclusion and freshness.

14. Integrations, APIs and data exchange

Can connected systems exchange data correctly through failure and replay? An API/integration contract with authentication, duplicate handling and reconciliation.

15. SEO, metadata and the URL lifecycle

Do public URLs, metadata and locale relationships express the intended page? A verified metadata/URL inventory, redirect map and international-discovery checks.

16. Accessibility for authors and visitors

Can authors and visitors complete the required tasks accessibly? An accessibility task matrix with accountable remediation and retest evidence.

17. Measurement, personalization and experimentation

Can the team trust measurement and personalized/default experiences? Event contracts and personalization/experiment acceptance evidence.

Release and run

18. Environments, pipelines, testing and release quality

Is a change compatible, tested and recoverable on the target environment? A release manifest, environment comparison, test results and hold/recovery authority.

19. Monitoring, maintenance, incidents and recovery

Who detects, investigates and recovers a failing service or content operation? Owned alerts, maintenance, incident records and a demonstrated recovery procedure.

Evolve the platform

20. Upgrades, migration, cutover and continuous improvement

Should we upgrade, migrate, launch, hold or retire the implementation? A compatibility/reconciliation record, cutover decision and owned improvement backlog.

Find a task or symptom

Scroll horizontally if needed.

Find a task or symptom: table 21
NeedStart with
Choose headless, pages or Edge Delivery1, 2, 5
Fix a blank editor or unusable dialog3, 4, 16
Protect local edits and translated references6, 7
Approve a change against the right baseline7, 10
Diagnose denied access or a failed API8, 11, 14
Release a page with the right media and references9, 10
Find a redirect or stale-content cause11, 15
Investigate slow queries or irrelevant search12, 13
Verify metadata or locale alternates6, 15
Validate analytics or a personalized/default experience14, 17
Accept a deployment or platform upgrade18, 20
Recover deleted content or a failing service19, 20

Review materials

Use the worksheets for actual decisions and tests. The evidence appendix records corpus scope, case limits and primary references.

Continue exploring

Adobe Experience ManagerAEM Sites

AEM Sites Playbook, Chapter 1: Strategy, value, ownership and adoption

What outcome justifies the work, and who will operate it?

Read more
Adobe Experience ManagerAEM Sites

AEM Sites Playbook, Chapter 10: Preview, publication, scheduling and withdrawal

How do we release and remove the complete approved experience?

Read more
Adobe Experience ManagerAEM Sites

AEM Sites Playbook, Chapter 11: Delivery, Dispatcher, CDN, domains and caching

Which layer controls the request, redirect or stale response?

Read more
Explore data and analytics services →