Platforms

Four platforms. One workspace.

Spectersync is a content engine, not a CMS. It connects to the platforms you already publish on and keeps a clean markdown copy of every post in step with the live site — same workflow, same syntax, same sync model for every one. The same connectors power the hosted workspace and the local editions.

Why one tool, every platform

Stop treating the CMS as the source of truth

The traditional answer is: pick a CMS and stick with it. That breaks the moment you run a Shopify storefront blog and a WordPress flagship for the same brand, syndicate a Ghost newsletter, or want to migrate without a six-month re-platforming project.

The folder is canonical

A clean markdown copy of every post is the source of truth. The CMSes are render targets. You write — or AI rewrites — in the workspace; Spectersync keeps every target in sync.

One brand, many surfaces

Run the same brand on three platforms without three separate workflows. A/B a piece on WordPress before promoting it to a Shopify storefront.

Migration without the project

Moving from one platform to another goes from a six-month project to “change the destination and click Sync.”

The connectors

Four connectors, one markdown format

Each connector reads and writes the same clean markdown. This page is the overview — for the precise pull/push surface per platform, see the Capabilities matrix.

Shopify

Shopify ships a blog system almost no one uses well — the article editor is a hidden corner of the admin and the AI add-ons charge per article. Spectersync pulls your articles into local markdown, you edit them with any AI, and it pushes back over the Admin API.

What round-trips today

Article body, title, handle, blog, author, status, scheduled date, tags, summary, SEO title & description, published-at.

Scope & support

Articles and blogs only — never orders, customers, products, inventory, themes, or payouts. The OAuth token lives in your macOS Keychain.

Connect Shopify

WordPress

The workhorse of the open web — and the most painful platform to run modern content ops on. The Block Editor is great for handcrafted pages and terrible for bulk work. Spectersync connects through the REST API with Application Passwords and turns the whole site into a folder.

What round-trips today

Post body (markdown ↔ HTML), title, slug, status, publish date, excerpt, featured image, tags, categories. Blocks without a clean markdown equivalent round-trip as raw HTML — preserved, never lost.

Scope & support

Self-hosted WordPress, WordPress.com Business+, and managed hosts (WP Engine, Kinsta, Pressable, Pantheon) that expose the standard REST endpoints.

Connect WordPress

Ghost

Where Spectersync started, and where support runs deepest. Ghost’s API is clean, its content model maps cleanly to markdown, and the typical Ghost user already lives in a text editor. Connect with your Admin API key and the connection persists in the Keychain.

What round-trips today

Posts, drafts, scheduled posts, pages, tags & tag metadata, authors, slugs, excerpts, feature image, published timestamps, meta titles & descriptions, OG/Twitter fields, and the featured flag.

Scope & support

Ghost 5.x and later — Ghost(Pro), self-hosted, or reverse-proxied. Lexical/mobiledoc card edge cases round-trip verbatim where markdown can’t represent them.

Connect Ghost

WebflowBeta

Webflow’s CMS is built for craft — a designer builds the template once, an editor fills one item at a time. That breaks at scale. Spectersync is the bulk-edit layer over the whole collection, connected through standard Webflow OAuth scoped to your CMS only.

What round-trips today

Collection items — name, slug, draft/published/archived state, rich-text body, plain-text, number & date fields, reference & multi-reference by item id, image fields by URL, and per-collection SEO fields.

Scope & support

Scoped to sites:read cms:read cms:write. The Designer, components, interactions, custom code, forms, Memberships, and Ecommerce are out of scope and never visible to Spectersync.

Connect Webflow

Cross-platform

Migration, multi-site, syndication

Because all four connectors read and write the same markdown folder, three workflows that used to be hard become easy.

Migration

Pull your old site into the folder, repoint Spectersync at the new platform, push. The body and the frontmatter that translates cleanly moves; platform-exclusive surface gets flagged in the Capabilities matrix so you know what needs a hand before launch.

Multi-site

One content team writing into one folder, with Spectersync syncing to several destinations — a Shopify storefront, a WordPress site, a Ghost newsletter, a Webflow brand site. Each CMS sees the same canonical version of every post.

Syndication

Publish primary on one platform, republish on another with a canonical link. Spectersync handles the duplication and the canonical metadata so the syndicated copy doesn’t compete with the original in search.

Deliberately not chasing

A focused tool, not a kitchen sink

  • Framer, Squarespace — closed platforms with no real public content API. We evaluated them; the round-trip fidelity isn’t there.
  • Headless CMS (Sanity, Contentful, Strapi) — already designed for code-first workflows, so Spectersync’s value is much lower there.
  • Drupal, Joomla, Craft — possible eventually, not on the near-term roadmap.

Publish primarily somewhere not on this page? Tell me what you’d use Spectersync for — the platform list is shaped by what real customers ask for.

Bring AI to your whole site

Shopify, WordPress, Ghost, Webflow — one workspace. Subscribe now and open with 500 free credits.