Approved in Content Hub, Live on the Site: Event-Driven Asset Publishing with Triggers and Next.js Revalidation
Sitecore Content Hub DAM + Next.js — a working implementation In most DAM-to-website setups, the moment the business cares about is approval. Legal signs off, the asset is marked Approved , and the campaign manager expects to see it on the site. What usually follows is a wait: for a cache to expire, for a scheduled job to run, or for someone to trigger a deploy. This article builds the alternative. When an asset’s status changes in Content Hub, the site’s cache for the affected campaign is invalidated within seconds — no rebuild, no polling. It includes working code for the three moving parts, the Content Hub configuration that connects them, and the section I spent the most time on: what happens when something in the chain fails. When this pattern applies. It fits sites that read approved assets from Content Hub at render time: campaign galleries, download centres, brand portals....