Adovo

AEM Sites Playbook, Chapter 9: Assets, media and Sites dependencies

Are media, references and delivery behavior ready for the experience?

November 10, 2026

Treat media as part of the content operation

Use this chapter when a page has missing, slow, incorrectly cropped or inaccessible media, or when Sites and Assets teams disagree about ownership. Identify each media dependency, its owner, intended use, rights/expiry information where applicable, source and required delivery behavior. Include the references that connect a page or fragment to the media.

Agree which metadata the asset team maintains and which the author may override in context. A reusable product image may have central descriptive information while needing a different text alternative on a particular page. The alt-text ownership discussion supports that distinction; do not assume a description or caption automatically becomes the correct rendered alternative.

For a hypothetical campaign, record the image, localized text alternative, crop, destination and replacement/withdrawal policy beside the page. Reviewers should see the intended image, not a broken reference or a stale rendition.

Separate processing from publication and delivery

Track whether upload/ingest completed, processing produced the required outputs, references are correct and the asset reached the intended destination. A page publication event alone does not establish these results. The Preview workflow case reports a page with broken images and overlapping processing. Its legacy workflow suggestion must not become Cloud Service implementation instructions.

Cloud Service uses the documented microservice processing model and configured post-processing; assess 6.5/LTS workflows in their own context. Define the handoff from processing to review/publication and how a failure reaches an operator. A repeated launcher or retry must have an understood effect on existing work.

Select the delivery mechanism actually in use

Distinguish Core Component image delivery, custom AssetDelivery Java API use and Dynamic Media interfaces. Check the available mechanism, supported parameters and rendering component before tuning size or quality. Adobe's web-optimized image documentation explains the Cloud Service behavior and fallback when the service is unavailable, including local development. Local output alone is insufficient evidence of the deployed image service.

The AssetDelivery size-option discussion includes many plausible formats, followed by the author's explicit statement that none worked. It mixes references to different API families. Use the Java API guidance for its intended interface; do not turn an unconfirmed parameter guess into a published recipe.

Measure the actual response dimensions, format, bytes and visual result on representative displays. Check long page content and slow connections from the project's test requirements. Optimization should preserve the meaning and quality needed for the customer task; a smaller file that crops out essential information fails that requirement.

Select a media contract rather than an attractive parameter

Community discussions separate file delivery from contextual meaning. An image API example records unsuccessful format attempts and mixed API references; the alt-text example concerns who supplies an appropriate description. Treat these as different acceptance concerns and verify the actual delivery interface and rendered alternative.

Scroll horizontally if needed.

Select a media contract rather than an attractive parameter: table 6
RequirementDecision to makeEvidence
Responsive image deliveryWhich supported component/service supplies the requested output?Actual dimensions, format, bytes and display result
Brand/locale cropWho chooses and approves the focal meaning?Representative narrow/wide views with real content
Shared descriptive metadataWhich centrally maintained fields are appropriate to reuse?Actual component fallback behavior
Page-specific alternativeWhich author may override it, and why?Rendered alternative in that context and locale
Expiring/replaced assetWhat happens to its references and cached delivery?Replacement/withdrawal test through the real route
Local SDK differs from cloudWhich behavior is a documented fallback?Target-environment test and recorded tooling/configuration

Use web-optimized image guidance and the Java API tutorial for their stated interfaces. A Dynamic Media command or GraphQL type with a similar name does not prove a Java option accepts that value.

Worked scenario of a product campaign image

The image sizes, limits and results in this scenario are hypothetical project requirements. A campaign reuses a product image on a listing page, detail page and localized promotion. The asset team maintains a central description. Regional authors may supply a contextual alternative for the promotion.

The team records the original asset/reference, required crop meanings, target viewports, delivery interface and processing state. It sets a project-specific payload budget and visual acceptance criteria before looking at optimization results. That budget is not an Adobe platform limit or a benchmark.

Scroll horizontally if needed.

Worked scenario of a product campaign image: table 9
UseRequired resultReviewer
ListingProduct remains identifiable at the required small layoutDesign/product owner
Detail pageRequired product detail remains legibleProduct owner
Localized promotionCrop and alternative support the local messageRegional content/accessibility owners
ReplacementAll intended references resolve to the approved revisionRelease owner
WithdrawalIntended visitors do not continue receiving disallowed contentContent/delivery owners

The engineer checks output in the deployed development environment, not only the local SDK. Authors preview the actual layout with long localized text. The release owner checks the dependency's destination and publication result.

Suppose the trial produces:

Scroll horizontally if needed.

Worked scenario of a product campaign image: table 11
CheckIllustrative observationDecision
Listing payloadBelow the agreed budgetThis performance condition passes
Narrow promotion cropRemoves essential product detailHold that use despite the smaller payload
Local alternativeRegional override is not emittedRepair component/content behavior
Local SDKUses a different delivery outputConfirm documented fallback before diagnosing a cloud defect
Replaced assetOne delivered route remains on the old revisionInvestigate reference/cache path before another broad republish

The team accepts the listing implementation within scope but holds the promotional use. A single asset can therefore have a valid use and an invalid use in the same release. The decision record must identify the actual component, context and route rather than mark the asset globally optimized.

Coordinate processing and publication without overlap

Give each processing state an owner and a clear handoff. A failed processing step should not be mistaken for an unpublished page, and an unpublished dependency should not trigger unnecessary reprocessing. Use the target platform's supported completion signal and inspect the actual result before adding custom launchers.

For Cloud Service, the microservice/post-processing model differs from legacy DAM workflow instructions. The Preview workflow case is useful because it exposes that handoff, not because its accepted implementation can be copied across deployments.

Retain the source, processing result, selected rendition/delivery contract, page reference and public observation in the same release evidence. If an asset is shared across many experiences, identify the owners who need review when it changes. Agree who may replace or withdraw it and what happens to downstream consumers.

Retain an operable media inventory

An inventory should let the operator answer where an asset is used, which revision is approved, what must be localized and who can resolve a failure. Keep rights/expiry decisions with the organization's content/legal owners. Include original-file custody and metadata/reference recovery in chapter 19 rather than equate a binary download with a complete backup.

Verify replacement and removal

Complete W09 with references, processing, rendition/delivery expectations, accessibility ownership and publication state. Test initial delivery, asset replacement, locale-specific use and withdrawal. Check caches and downstream consumers after a removal. If original files are exported for backup, document what metadata, references and permissions the export omits; the bulk-backup question does not establish a complete recovery solution. Use chapter 19 for the recovery objective and restore test.

W09 Media dependency and delivery

Use with chapter 9. Link the media record to its page/fragment release.

Scroll horizontally if needed.

W09 Media dependency and delivery: table 17
RecordEntry
Asset/reference, source owner and intended use[enter]
Processing, metadata, rights/expiry responsibility and destination[enter]
Delivery interface, supported parameters and target environment[enter]
Required dimensions/crop, format, visual quality and observed bytes[enter]
Alternative/decorative treatment, locale and override owner[enter]
Replace/withdraw, cache and downstream-reference test[enter]

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 →