Platform

The editorial operating layer for Framer client sites.

ContentPilot separates client content work from your Framer build. Developers configure the site once; writers draft in a guided portal; editors approve before anything reaches production.

Start free See plans

ContentPilot article approved and ready to publish — Approved content, ready for Framer

Workflow

Write, review, approve, publish, sync.

ContentPilot gives every participant a clear lane, then moves approved content to Framer without exposing your build.

Write

Clients draft posts in ContentPilot.

Review

Editors check structure, metadata, and readiness.

Approve

Only reviewed content moves toward publishing.

Publish

Approved articles become the source of truth.

Sync

Framer renders from the API or receives CMS entries.

Setup

What developers package for each client.

The setup path mirrors the real handoff: configure the Framer destination, define the editorial fields, then invite the client team only after the content lane is ready.

Create a workspace

The developer starts the client content environment and chooses site capacity.

Connect Framer

Add the production origin, route pattern, and optional Framer API sync settings.

Define article fields

Choose built-in and custom fields so writers produce stable CMS-ready content.

Invite client users

Give writers, editors, and stakeholders the right role and site access.

Publish approved content

Move articles through review before Framer renders or receives synced content.

Delivery

Two ways to connect approved content to Framer.

ContentPilot remains the editorial source of truth. Each client site can use the delivery model that fits the build.

Render from the ContentPilot API

Use a Framer code component to read published posts from ContentPilot. This keeps setup fast when Framer only needs to display approved content.

Sync into Framer CMS

Use the ContentPilot CMS plugin when teams want native Framer collections for articles, authors, tags, images, and SEO fields.

ContentPilot review workflow with Framer delivery settings — Review, approve, deliver

Two audiences

Developers keep control. Clients get autonomy.

The buyer and the daily user both get a better workflow: one side protects the Framer build, the other side gets a simple way to write and submit content.

For Framer developers

Protect the implementation while giving every client a real editorial process.

Protect your Framer build and CMS structure

Keep clients out of design and field settings

Define article structure once per connected site

Publish through a predictable approval flow

For client content teams

Write, review, and track content without navigating design tools or CMS settings.

Write in a focused editorial portal

Submit drafts without learning Framer CMS

Track review status and requested changes

Collaborate with editors before content goes live

Ready for a client-safe Framer content workflow?

Create a workspace, connect your first Framer site, and invite writers into ContentPilot instead of your website backend.

Start free Compare plans