“Looks good in the CMS form” is not review.
Authors and stakeholders need a URL that renders the page as production would — with the right templates, partials, and personalization rules either applied or clearly labeled. AEM, headless CMSs, and static preview deploys solve this differently; the product requirement is the same.
Show the page before it is the page of record.
Requirements that make preview real
- Unique link per draft or version
- Auth or secret token; never publicly indexable
noindexand preferably a separate host- Visible banner: “Preview — not live”
- Safe datasets; no production secrets or real PII
- Link expiry so abandoned drafts do not live forever
Failure modes we keep seeing
- Preview CSS/JS differs from production (false approvals)
- Editors share infinite-lived open links in public Slack
- Preview hits production APIs and mutates real data
- No preview for localized or personalized variants
- “Screenshot the authoring UI” as the only review path
Edge Delivery and AEM notes
Document-based and Universal Editor workflows still need a publish-like preview of the composed page. If preview is “open the Word doc,” you are not reviewing the experience customers get.
Closing
Budget preview as part of the content model, not a nice-to-have. It is how editorial quality scales without engineering in the loop for every comma.
Need preview environments for CMS or Edge Delivery? Start a project inquiry.
Stakeholders
Preview is for authors, brand, legal, and sometimes clients. Each needs the right access level. Clients should not see other clients’ drafts.
Performance of preview
Preview can be slower than prod, but not a different layout system. If preview uses a different design system build, approvals are meaningless.
Personalization
Show a control to simulate segment/locale. Default to “anonymous public” so reviewers see the common case.
Audit trail
Log who opened which preview when dealing with regulated content. Pair with CMS version history.
Implementation patterns
- Branch deploys for static sites (Netlify/Vercel-style previews)
- CMS preview SDK for headless (tokenized draft queries)
- AEM preview / Universal Editor live canvas with publish simulation
- Edge Delivery preview channels tied to the content source
Whichever you pick, document the author steps in two screenshots max.
Security review
Preview tokens in URLs leak via Referer logs and chat. Prefer short TTL, auth walls, and separate hostnames that never share production session cookies.
Comparison table
| Approach | Best for | Watch-outs |
|---|---|---|
| Branch deploy preview | Static/marketing sites | Secrets in preview env |
| CMS draft preview | Editorial workflows | Parity with live templates |
| Tokenized headless preview | App-like frontends | Token leakage |
| Shared staging content | Early collaboration | Cross-client data bleed |
Definition of done for preview
A content PR/change is not reviewable until a preview link exists, loads without VPN drama for the intended reviewers, and shows the same components as production.