Built with AI
How to let a client edit a site you built with Claude Code
Push the site to GitHub, connect the repository to Siteshare, and invite your client. They open their own site with /edit at the end of the address and change texts, photos and sections by chatting, selecting or typing on the page. You keep building in the same repository with Claude Code. There is nothing to move into a CMS first: your code is the content model.
- 01
Put the site on GitHub
Ask Claude Code to commit and push the site to a GitHub repository. A private repository is fine. Siteshare works with GitHub only, for now.
- 02
Connect the repository
In the site's folder, run npx siteshare connect. It reads the repository from git and opens Add a site in Siteshare with it filled in. Or install the Siteshare plugin for Claude Code and ask Claude to hand the site over; it runs the same command.
- 03
Give the GitHub App access and add the site
Install the Siteshare GitHub App on that one repository. Siteshare builds the site once, the way your host would, so you see straight away that it runs.
- 04
Invite your client
Invite them from the site's page with their email address and choose how far they may go: Text and images, Blocks and pages, Design or Everything. Anything above that waits for your approval.
- 05
Keep building, and pull first
What your client publishes is one commit on main. Pull before you start a session in Claude Code, as you would with any colleague.
Why not a CMS?
When Claude Code builds a site, the texts usually sit in the pages and components themselves. Most CMSs want that content moved into data files or a database first, with every field described. Ask Claude Code which CMS to use at handover and that is often its answer: move the content, then add Pages CMS, Decap or TinaCMS.
Siteshare skips that step. Your client points at what should change or asks for it, and the assistant edits the code where the content is. You keep the site exactly as you built it.
What stays yours
Your repository, your host and your code. Siteshare hosts nothing: publishing is one commit on main, after a build on a clean copy. Configuration, packages and server code are protected by default, and a change there waits for you.
Questions
Can my client just use Claude Code themselves?
They could, with access to the repository and a terminal. But nothing then stops a change from going live unchecked. Siteshare gives them drafts on the real site, a build check before anything goes live, limits per client and a way back.
Do I need to change my code for Siteshare?
No. There's no schema to write and no content to move into files. The assistant edits the files where the text actually is, including inside components.
Can Claude Code connect the site for me?
Yes. With the plugin, Claude Code knows when a site is ready to hand over and runs npx siteshare connect. It never signs in, invites or publishes for you: you open the link and add the site yourself.
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.
What does it cost?
Free for one site. Then $9 a site a month, less as you grow: five sites cost $36 a month and twenty $126, with clients and builders unlimited and the assistant with fair use.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.