Publishing to your website
WordPresto is CMS-agnostic. The Canvas produces approved, structured content, which then enters destination preparation and handoff. Publishing never happens before content is approved, and WordPresto supports three website destinations: WordPress, Sanity and a connected site repository.
The Publish to… flyout
Section titled “The Publish to… flyout”In the Canvas toolbar, the Publish to… control gathers every destination — social channels and website destinations — behind one trigger, so the rail stays tidy as destinations grow. A website destination appears there when the project has it connected (Project Settings → Destinations).
Approval comes first
Section titled “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.
The three website destinations
Section titled “The three website destinations”Each has its own guide, because they work differently and the differences matter:
- Publishing to WordPress — the only destination that can publish live, and the only one that re-reads the live page afterwards to confirm what actually shipped.
- Publishing to Sanity — drafts only. Your team publishes from Sanity Studio, so your review flow stays in charge.
- Publishing to an Astro site or site repository — edits your real source files and opens a pull request. Nothing is written until you approve the diff.
Preparation and pre-flight
Section titled “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 checks that the destination’s requirements are met before anything is written. If schema or a mapping is missing, WordPresto reports exactly what is required.
Safe by default
Section titled “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.
