Built with AI
How to let a client edit a site you built with Cursor
Keep the site in a GitHub repository, connect it to Siteshare, and invite your client. They edit the real site at their own address with /edit at the end, by chatting, selecting or typing on the page. You keep working in Cursor on the same repository. Nothing has to move into a CMS first.
- 01
Keep the site on GitHub
Commit and push from Cursor to a GitHub repository. If you use Cursor's own Origin repositories, use one that mirrors GitHub: Siteshare connects to GitHub only, for now.
- 02
Connect the repository
In Cursor's terminal, in the site's folder, run npx siteshare connect. It opens Add a site in Siteshare with the repository filled in.
- 03
Give the GitHub App access and add the site
Install the Siteshare GitHub App on that repository. Siteshare builds the site once, the way your host would.
- 04
Invite your client
Invite them with their email address and choose their level: Text and images, Blocks and pages, Design or Everything. Anything above it waits for your approval.
- 05
Keep building
A client's change goes live as one commit on main. Pull before you start, and let Cursor's agents work on their own branches as usual.
The handover, without a rebuild
A site built in Cursor looks like any other codebase: pages, components and the texts inside them. Siteshare reads it as it is. Your client asks “change the opening hours” or selects the heading and types, sees the change in a draft on the real site, and presses Publish.
Before anything goes live, Siteshare builds exactly the files that will go live on a clean copy. Only a site that builds gets one commit on main.
Questions
Does Siteshare work with Cursor's cloud agents?
Yes, side by side. Cloud agents push to their own branches; your client's drafts live on Siteshare's draft branch, and only Publish touches main.
Do I need to add a CMS to my Cursor project?
No. Siteshare edits the files where the content is, so there are no fields to describe and nothing to move.
Which hosts work?
Any host that publishes from main. Tested on Cloudflare, Netlify and Vercel. On Vercel, turn off previews of the draft branch in vercel.json. On a private repository in a GitHub organization, Netlify and Vercel may hold back commits by an author outside your team there, so allow the commits Siteshare makes.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.