Client editing for Framer
Let clients edit your Framer site.
The design was done in Framer and the client loved it. Now they want to edit the copy themselves, and the choice is a Framer editor seat per person, or you exporting the site to code and losing the editing entirely.
Tusk is a client editing layer for sites you already built. You keep the code, the repo and the hosting. Tusk marks the text, photos and downloads the client may change, and the client changes them on their own live page. Nothing of Tusk runs between a visitor and the site.
Getting the site out of Framer
- Export the site to HTML (Framer’s HTML export, or a static crawl of the published site) and put it in a repo. It is plain HTML, CSS and a little JS.
- Deploy the repo on Cloudflare Pages, Netlify or Vercel. Any of them gives you a deploy hook.
- Open the repo in an agent (Claude Code, Cursor, Codex) or mark the HTML by hand.
Connecting it, step by step
- Add the Tusk MCP to the agent, or add one data-tusk attribute per editable element yourself.
- Log in once for this site: npx @tuskcms/mcp login --site <slug>.
- Say “Connect this site to Tusk CMS.” It marks the text, photos and downloads in the exported HTML, adds the build step, sets up the deploy hook with you, publishes and verifies.
- Invite the client. They edit the words on the exported site, no Framer seat.
The MCP config, for Claude Code, Cursor, Codex or Windsurf. Nothing to install: it runs from npm on demand.
{ "mcpServers": { "tusk": { "command": "npx", "args": ["-y", "@tuskcms/mcp"] } } }No MCP? Paste this one line into any AI tool that can read a URL and edit files:
Connect this site to Tusk CMS. Read https://tuskcms.com/llms-full.txt first and follow it exactly.
Start from a template
The Tusk starter is a GitHub template: a three-page business site in plain HTML, already marked up, with the build step and Vercel and Netlify config in place. Use the template, deploy it, say “Connect this site to Tusk CMS.”, and hand it to the client. Then reshape it into their site.
Starting from a prompt instead? Ask your tool to build the site with the marks in from the start: the first-prompt version works in any builder.
What the client gets
- Their own login. They open an editor with a live preview of their real website beside the fields you marked, click a heading, a paragraph, a photo or a download, change it, and press Publish.
- Nothing of yours. No repo, no Framer, no code, no layout or styles. What you did not mark cannot be edited.
- History of the last 30 days, with any version restored as a draft, so a bad edit is never permanent.
- A Publish that reaches the live site through your own host, and a dashboard that tells you both whether it did.
What you keep
- The codebase, the hosting and the deploy. Tusk triggers a deploy hook you own, and that link, encrypted, is all it holds of your host.
- A static site that stays static: published content and images are written into your build by two zero-dependency scripts. The deployed site never calls Tusk.
- The retainer. The client pays you; you pay Tusk by site. Clients never pay for their login.
- The exit. Export gives you a site’s words, photos, fields and 30 days of versions as files; disconnect cuts every tie and the site keeps serving.
Questions Framer developers ask
I still want to redesign in Framer later.
You can. Export again, re-run the connect prompt, and the published content is re-applied by field name. Content lives in Tusk keyed by field, not by file, so a fresh export does not lose the client’s edits.
Framer’s CMS collections?
In the exported HTML a Framer CMS collection is a repeated block, which is marked as a Tusk list field: the client can edit, add and reorder items. If the collection drives many pages, tell the agent which page each item belongs to.
Why not just buy Framer seats?
You can. Tusk is for the case where the site has left Framer, or where the client should touch only the words and never the design.
Also built with plain HTML, Astro, Claude Code? Tusk works the same way. All builders: Lovable, v0, Bolt, Replit, Claude Code, Codex, Cursor, Windsurf, Next.js, Astro, Eleventy, plain HTML, and any site with a build step or deploy hook.