Capabilities
Capabilities
Specter’s core job is to pull CMS content into local Markdown, let you edit it with the tools you already use, and push reviewed changes back. This is the current matrix: what works today, what is partial, and what is still in development.
For timing and priorities, see the roadmap. For shipped release notes, see the changelog.
Platform matrix
| Platform | Status | Pull | Push | Content supported | Not yet |
|---|---|---|---|---|---|
| Ghost | Available | Pull posts into local Markdown with frontmatter. | Push local edits back to existing posts or create new posts and pages. | Posts and pages (each opt-in per connection), drafts, scheduled posts, tags, authors, excerpts, slugs, status, published dates, featured image URLs, and local image upload. | Full-fidelity editing for every complex Ghost card. |
| Shopify | Available | Pull blog articles, pages, and products across Shopify into a dedicated store folder. | Push article, page, and product edits back to Shopify, including creates and updates. | Articles, pages, and products (each opt-in per connection; products are description-first), draft/published state, handles, summaries, tags, authors, blog containers, and featured image URLs. | Product variants, inventory, and pricing; theme files; local image upload. |
| WordPress | Available | Pull WordPress posts and pages into local Markdown. | Push local edits back to posts and pages using WordPress Application Passwords. | Posts and pages (each opt-in per connection), drafts, scheduled posts, categories, tags, slugs, excerpts, status, dates, featured image URLs, and local image upload (assigned as featured media). | Custom post types, WordPress.com OAuth, Jetpack-specific flows. |
| Webflow | Available · beta | Pull CMS collection items into local Markdown with frontmatter for the fields each collection exposes. | Push local edits back to existing CMS items, and create new items in the collections you've authorized. | CMS collection items (each opt-in per connection), name, slug, draft / published / archived state, rich-text body, plain-text / number / date / option / link / color fields, reference and multi-reference fields by item id, image fields by URL, and per-collection SEO fields. | The Designer, page structure, components, interactions, custom code, forms, Memberships, Webflow Ecommerce, redirects, hosting settings, and local image upload. |
| Sanity | Planned | Planned after demand is clearer. | Planned after schema mapping is scoped. | Likely document types that behave like articles or posts. | Arbitrary schemas, custom portable-text blocks, and asset workflows until a real project drives the adapter. |
| Contentful | Planned | Planned after demand is clearer. | Planned after content model mapping is scoped. | Likely entry types that behave like articles or posts. | Arbitrary content models, references, localization, and asset workflows until the adapter is designed. |
| Strapi | Planned | Planned after demand is clearer. | Planned after API and content-type mapping is scoped. | Likely article-like collection types. | Custom content types, relation-heavy models, and media upload until a real Strapi project defines the edge cases. |
Feature matrix
| Capability | Ghost | Shopify | WordPress | Webflow |
|---|---|---|---|---|
| Pull to local Markdown | Supported | Supported | Supported | Beta |
| Push edited content back | Supported | Supported | Supported | Beta |
| Create new content from local files | Supported | Supported | Supported | Beta |
| Posts or articles | Supported | Supported | Supported | CMS items first |
| Pages (opt-in per connection) | Supported | Supported | Supported | Not promised |
| Products (opt-in, description-first) | n/a | Supported | n/a | n/a |
| Tags/categories/blog containers | Supported | Supported | Supported | Depends on collection |
| Draft and published state | Supported | Supported | Supported | Beta |
| Featured image URLs | Referenced | Referenced | Referenced | Beta |
| Upload local images | Supported | Planned | Supported | Not yet |
| Dry-run preview before publishing | Supported | Supported | Supported | Planned |
How to read this
Supported means the capability is in the released Mac app. Opt-in per connection means you choose which content kinds each connection syncs — nothing is on by default, so a connection only pulls and pushes the kinds you turn on (posts, pages, products). Referenced means Specter keeps the remote URL in frontmatter but does not upload a local image file yet. Beta means the capability is in the released app but fidelity for the rarer edge cases is still being expanded — safe for production with a Preview-Sync diff in the loop. Planned means it belongs on the roadmap but is not the next thing you should bet production work on.
The practical rule: if your workflow is Markdown-first posts or articles, Specter is already useful today. If your workflow depends on pages, media uploads, custom content models, or highly designed blocks, check the matrix before you plan a big migration.