Seamless Integration of Experience Manager Assets with Applications
summary
AEM Assets exposes an open API delivery and search stack that delivers brand-approved assets to external CMSes via a plug‑in or direct API calls. The demo shows a JavaScript asset selector UI component (pojs.selectors.renderAssetSelector) that returns repositoryId, assetId, name and dynamic delivery URLs, plus a WordPress plugin using the search API and API Playground. Clients can be auto-generated with OpenAPI/codegen or a Maven plugin. Delivery supports dynamic renditions and adaptive video (HLS/DASH); approval propagates to delivery/search with 95th‑percentile under 10 minutes.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:04Use case and requirements
- 3:10New asset delivery innovation
- 6:22Asset selector UI component
- 9:18Demo approval and WordPress
- 12:20Delivery API specification
- 15:32Integration details
- 20:30Search API integration
- 22:00WordPress plugin demo
- 24:10API playground and queries
- 27:00API client generation
- 28:32Developer benefits
- 29:58Resources and next steps
- 30:39Q&A session
related talks
39mAdobe Experience Manager as a Headless CMS - Where/When/Why?
28mAdobe Workfront and Adobe Experience Manager Assets
46mThe Past, Present, and Future of Adobe Experience Manager
54mAdobe Experience Manager Rock Star: The Headless Challenge
30mExperience Manager Extension for PWA Studio
28mCustom Adobe Experience Manager Assets Compute Worker with App Builder
02mAEM Shorts: Content Reuse and Omnichannel Delivery with AEM
28mWhat's new in Adobe Experience Manager Assets as a Cloud Service