For end users

How does publish work?

This is the bundled content-publishing path. When a draft is ready in the page builder, click Publish. Pectus resolves the page’s URL (mount slug + locale prefix + materialized path + slug), generates the page JSON, updates the workspace’s site plan, and ships everything as one commit to the GitHub repo configured at Workspace → Content Insights → Site URL. The content-insights site reads from that repo at build time.

Slug changes: Pectus tracks the old URL and proposes a redirect on next publish. Approve and the redirect lands in content/redirects.json, which the hub’s middleware serves as 301s.

Other outbound apps (a WordPress publisher, a Webflow publisher, a custom ingest endpoint) follow their own publish path — see apps-spec.