Home | Connectors | WoodWing | WoodWing - Adobe Experience Manager Sites Integration and Automation
WoodWing and Adobe Experience Manager Sites complement each other well in enterprise content operations. WoodWing is strong in managing rich media, product imagery, publishing assets, and campaign files, while Adobe Experience Manager Sites is designed to assemble, govern, and deliver those assets within web and mobile experiences. Integrating the two platforms helps teams centralize asset production, streamline content reuse, and keep customer-facing experiences current across channels.
:Data flow: WoodWing to Adobe Experience Manager Sites
:Marketing and product teams can manage master product photography in WoodWing, then automatically push approved renditions and metadata into Adobe Experience Manager Sites for use on product detail pages, category pages, and campaign landing pages. This ensures web teams always work with the latest approved visuals without manually downloading and re-uploading files.
:Data flow: WoodWing to Adobe Experience Manager Sites
:Campaign banners, hero images, videos, and supporting creative can be finalized in WoodWing and then delivered to Adobe Experience Manager Sites for reuse across web pages, microsites, and mobile experiences. This is especially useful for seasonal promotions, product launches, and event-driven campaigns where multiple digital properties need the same approved content.
:Data flow: WoodWing to Adobe Experience Manager Sites
:Content authors in Adobe Experience Manager Sites can browse and insert WoodWing-managed images and videos directly into page components. This gives web teams access to a controlled asset library while allowing WoodWing to remain the system of record for media production and approval.
:Data flow: Adobe Experience Manager Sites to WoodWing
:When assets are used in live pages, Adobe Experience Manager Sites can send usage information, page references, or campaign context back to WoodWing. This helps content managers understand where assets are deployed, which versions are active, and whether an asset needs replacement or retirement.
:Data flow: WoodWing to Adobe Experience Manager Sites
:For publishers and content-rich organizations, WoodWing can store book imagery, layouts, photography, and editorial assets, while Adobe Experience Manager Sites uses selected assets to build article pages, author profiles, book landing pages, and promotional content. This is valuable for organizations that need to repurpose editorial materials into web experiences quickly.
:Data flow: WoodWing to Adobe Experience Manager Sites
:Museums and heritage organizations can store high-resolution photos and videos of collections in WoodWing, then publish curated selections to Adobe Experience Manager Sites for online exhibitions, collection highlights, educational pages, and donor engagement content. Metadata such as collection name, period, and rights information can travel with the asset to support accurate presentation.
:Data flow: WoodWing to Adobe Experience Manager Sites
:After conferences, product launches, or company events, approved photos and video clips can be stored in WoodWing and then published to Adobe Experience Manager Sites for recap pages, press sections, recruitment pages, and social proof content. This creates a fast path from event capture to web publication.
:Data flow: Bi-directional
:WoodWing can manage asset creation, review, and approval, while Adobe Experience Manager Sites can manage page assembly and content delivery. A bi-directional integration can pass approval status, version updates, and publication references between systems so that only approved assets are exposed on live pages and any asset changes are reflected in the web experience.
:Overall, integrating WoodWing with Adobe Experience Manager Sites helps organizations connect asset production with digital experience delivery. The result is faster publishing, stronger governance, better reuse of approved content, and less manual work for marketing, publishing, and web teams.