Next-Gen Content Workflows in Strapi
summary
Strapi 5 Preview embeds front ends inside the admin using a single iframe proxy whose source is computed by a config function that can point to a Next.js API endpoint; that endpoint sets a draft-mode cookie to let previews show unpublished content without affecting production. The proxy forwards editor events via postMessage forwarding to nested iframes, hosts a device selector and QR flow for Expo development builds, and implements field-level highlight updates so real-time, multi-platform preview workflows actually work.
AI-written summary · about
chapters (10)
- 0:00Introduction: Why Strapi 5 Preview is a Game Changer
- 1:23How the Preview Feature Works (Behind the Scenes)
- 2:59Setting Up Preview with Strapi Launchpad
- 5:15Multi-Frontend Preview Setup: Web + Native
- 6:31Creating a Custom Proxy Page Inside Strapi Admin
- 9:46Supporting Preview in Web and Mobile Apps
- 14:24Handling Real-Time Preview Changes and Events
- 18:58Responsive Preview Across Devices (Web, Tablet, Mobile)
- 20:26Further Customizations: Highlight Changes, Device Views
- 22:28Final Thoughts: Why Preview Empowers Content Teams
related talks
22mNuances of Iframe: Lessons from Contentstack Live Preview
31mEditorial workflows, GIT them here!
15mBuilding Modern CMS Driven Web Applications with Next.js
20mWebstrates: Shareable Dynamic Media
09mFrom 0 to Strapi in Production in 60 days
07mBoosting Productivity and Team Velocity with Strapi
24mThe Future of Editing Websites
08mHeadless - The Future of CMS Is Here
