Integrations

Meet teams where they already publish

The product direction supports both classic CMS flows — now including Wix and Ghost — and modern TypeScript-site teams that need secure delivery, rebuild hooks, or eventually repo-based publishing.

Live adapters in the current backend slice

Live adapter

WordPress

Application-password validation, post create/update flows, and reusable destination IDs for repeat publishing.

• Verified credentials and permissions
• Draft and live publish modes
• Stored published URL and overwrite path

Live adapter

Webflow

Collection-aware publishing with field validation, domain matching, and live-publish guardrails.

• Collection slug and content field checks
• Staged versus live publishing control
• Published URL generation when live

Live adapter

Shopify

Blog-aware article publishing via Admin GraphQL with shop validation and explicit live-publish permission.

• Storefront domain verification
• Reusable article destination IDs
• Draft and live blog publishing

Live adapter

Wix

Draft-post publishing with site verification, API-key validation, and optional live release when the connection allows it.

• Site ID and Manage Blog permission checks
• Draft-first publishing with optional live release
• Reusable draft destination IDs for repeat updates

Live adapter

Ghost

Ghost Admin API publishing with site validation, HTML delivery, and reusable post IDs for safer repeat publishing.

• HTTPS site and admin-key verification
• Draft and live publish modes
• Published post URLs captured after successful delivery

Live adapter

Secure webhook

A clean bridge for custom stacks that want signed payloads, dedupe keys, retries, and stable destination IDs.

• Public HTTPS targets only
• Bearer or custom header authentication
• Deterministic dedupe keys for article delivery

Planned first-class support for modern web teams

Next.js / Astro / Remix

Planned first-class

The landing story makes our TypeScript direction explicit: webhook, revalidation, and content-store friendly patterns from day one.

• Webhook-friendly route handlers and server endpoints
• Revalidation or rebuild-driven publish modes
• Future Git / PR content recipes for repo-owned blogs

Headless and repo flows

Planned next

Future support is aimed at teams that want PR-reviewed content, headless CMS bridges, or static-site rebuild orchestration.

• Headless CMS bridge mode
• Revalidation trigger and rebuild workflows
• Git / PR publishing for docs-style content repos

Integration philosophy

Native when obvious

WordPress, Webflow, Shopify, Wix, and Ghost should feel direct because they already speak content APIs.

Webhook when flexible

Custom sites should receive signed payloads, dedupe keys, and stable destination IDs rather than bespoke manual glue.

Repo or rebuild when safer

Teams with static or repo-owned content often need reviewability more than raw direct publish.