Publishing to WordPress and Sanity

WordPresto is CMS-agnostic. The Canvas produces approved, structured content, which then enters destination preparation and handoff. Publishing never happens before content is approved.

The Publish to… flyout

In the Canvas toolbar, the Publish to… control gathers every destination — social channels and CMS destinations (WordPress, Sanity) — behind one trigger, so the rail stays tidy as destinations grow. WordPress and Sanity appear there when the project has that destination connected.

Approval comes first

Publishing is gated on approval. Approval means the required review Workers have run, relevant suggestions have been accepted, rejected or resolved, final editorial approval has been given, and the content is ready for handoff. Until then, publishing agents do not write to any external system.

Preparation and pre-flight

A Builder Worker prepares the approved content for the selected destination — frontmatter or fields, slug, metadata, schema and media references — and a publishing pre-flight Worker checks that the destination’s requirements are met (a Sanity document type and mapped fields; WordPress post type and media). If schema or a mapping is missing, WordPresto reports exactly what is required rather than inventing a field.

Safe by default

By default WordPresto prepares the destination package and shows a preview or handoff, creating a draft only when supported and approved. Live publishing needs an explicit action. WordPresto never publishes automatically from an unapproved Canvas, never fakes a successful publish, and never silently discards content blocks a destination cannot represent — unsupported blocks are reported.