Let editors review the right draft in its website context.
A headless CMS can hold drafts without the website offering a working preview. ImbaHub can integrate a focused preview route between source and page. We separate draft access from public delivery and assess the actual installation. This is separate development, rather than a promised standard Imba CMS feature.
- Published
The public website reads intended approved content.
- Preview
An authorised editor reviews an identified draft.
- Decision
Preview does not replace approval or public verification.
Matching appearance does not mean matching source or access.
Preview has new text but the public page is old. Is publication verified?
No. You saw preview evidence. Follow the separate publishing step and inspect the actual public page.
Connect the record to the right view and environment
Start with one content type and a clear record identifier. Define its website route and how language and content environment are selected. A staging record must not be mistaken for production merely because its name resembles a public page.
Fictional example: an editor changes a service description and needs to check mobile layout before approval. Preview should show the identified draft version in the right language while the public page retains its intended published content.
Choose a delivery model that can show drafts
Preview may need a separate protected environment, a new preview build or an on-demand route. Choose around the technology and how quickly editors need saved changes. Astro on-demand rendering needs a suitable server adapter; a static build does not become dynamic because its name includes preview.
A CMS may provide separate draft access. Handle permissions and secrets for the chosen design, keeping them distinct from public content delivery. We do not promise a named connection before reviewing API, hosting and access.
| Element | Decision before integration | Exercise |
|---|---|---|
| Record | Which identifier and page model? | Right draft in the right view |
| Language | How are language and fallback selected? | No unlabelled wrong-language version |
| Environment | Which source may preview read? | Test source is not confused with production |
| Access | Who sees drafts and how does access end? | Anonymous and revoked routes tested |
| Freshness | When does a saved edit appear? | Editor can establish the actual version |
Make preview and published content distinguishable
Editors need to know what they are reviewing and whether saving or rebuilding remains. An old preview must not be used as evidence for a new edit. Clear status and controlled updating matter more than promises of instant synchronisation.
Preview must not unintentionally create public sitemaps, search indexes or cached drafts. Indexing instructions are not access protection. Test access and data delivery rather than only a warning banner.
Deliver one tested editorial route
An initial delivery can cover one record type, one language, a protected view and a clear return to editing. Live updates, visual field highlighting and additional types are separate capabilities where required. Invented product screens are not used as evidence.
Handover covers source, environment, access, version checks, revocation and failures. We propose scope and price after review. Show a representative synthetic draft and how the editor needs to assess it.
Sources and further reading
Questions, answered
Is preview the same as publication?
No. Editors review evidence; public delivery needs its own intentional step.
Can noindex alone protect preview?
No. It does not replace checks on who may fetch drafts and related resources.