Previewing content with confidence

Review content in its real context

A form view is excellent for editing structured information, but it cannot answer every publishing question. Editors also need to see hierarchy, spacing, image crops, related documents, and localized routes. A dependable preview joins those perspectives without turning the preview itself into a second content system.

Our product and engineering team includes previews in the implementation service. The connection follows Sanity’s visual editing guidance so contributors can move directly between a rendered element and the field that controls it.

Make preview behavior predictable

Preview URLs are derived from the same route rules as the published site. Draft perspective is authenticated, reference changes update together, and missing translations fall back visibly rather than silently disappearing. Clear empty states explain whether content is incomplete, unavailable, or intentionally hidden.

• Keep route resolution in one tested place so previews and published pages cannot drift apart.
• Show draft and published context clearly, especially when references point to documents at different stages.
• Exercise previews for both locales, nested routes, access restrictions, and modal navigation.

A good preview does more than resemble production: it explains what the editor is seeing and why.

Turn review findings into durable checks

When a preview reveals a broken crop, missing reference, or ambiguous fallback, we add a focused validation or regression test. That feedback loop keeps the tool useful as schemas and routes evolve. Editors gain confidence because the preview represents the same content graph the production renderer will use.