Fixes arrive the way your stack accepts them.
Today, every fix is written out for you to apply yourself, on every platform. The scan API is live. Connectors are in progress: CMS drafts first, then repository delivery. Each page below says which.
The delivery modes
Every platform lands on one of these rungs, and the verification label follows the rung rather than the marketing.
| Mode | What we get | How changes arrive | Verified | Status |
|---|---|---|---|---|
| A · Repo write | A repo we can push a branch to | Pull request; you review and merge | Build | In progress |
| B · Read-only repo | Read access plus somewhere to push | Branch or fork you own | Build | In progress |
| C · Cloud mirror | A snapshot or export | Patch or PR from a clone | Build (mirror) | In progress |
| D · CMS drafts | OAuth into a hosted CMS | Unpublished drafts; you publish | Preview | In progress |
| E · URL only | A public URL | Written-out fixes; you apply | Advisory | Live |
Build-verified means a build ran. It applies to A, B and C and nothing else. A hosted CMS has no build, so D is preview-verified and E is advisory. Those labels are never blurred.
Build
Live: automate scans and read scorecards from your own code.
Mode E Live WebhooksGet told when a scan finishes or a fix is ready.
Mode E In progress ZapierRoute scan results into whatever your team already uses.
Mode E In progress Next.jsFixes as a pull request, built before you see it.
Mode A In progressPlatforms
Changes will land as unpublished drafts.
Mode D In progress WebflowCMS collection items updated as drafts.
Mode D In progress ShopifyProduct and page metadata via the Admin API.
Mode D In progress SquarespaceAdvisory only: a checklist you apply by hand.
Mode E In progress GhostPost metadata and content as drafts.
Mode D In progressMore platforms
Platforms with no content-write API
Squarespace, Framer and Unicorn Platform have no supported way for a third party to write page content or metadata. They sit on Mode E, and the findings arrive as instructions you apply in the editor. Claiming otherwise would be inventing a capability, and those pages say so plainly rather than implying a connector is coming.