Guides
Guides for builders.
Which CMS fits a site you built with AI, and how to hand it over to the people it's for. With dated facts and sources; we make Siteshare, and say so where it's on a list.
Choosing a CMS, or none
The best CMS for Astro in 2026
Ten ways to let editors change an Astro site in 2026, from free Git-based editors to headless platforms, with prices, setup and limits, checked October 2026.
The best CMS for Next.js in 2026
Ten ways to let editors change a Next.js site in 2026: Git-based editors, headless platforms and visual builders, with prices and limits, checked October 2026.
WordPress alternatives for client sites
Eight alternatives to WordPress for agencies and freelancers who hand sites over to clients: how clients edit, what it costs per client, and who owns the code.
How to let a client edit a site you built with AI
You built the site with Claude Code, Cursor, Lovable or v0. Six ways to let your client change it themselves, and a handover checklist that keeps the code safe.
Do I need a CMS for my client's website?
Often not. If the content lives in the site's own code and goes to one website, an editor on the site is enough. When a CMS is the better choice, and why.
Built with an AI tool
How to let a client edit a site you built with Claude Code
Your site is code in a repository. Push it to GitHub, connect it to Siteshare, and invite your client: they edit the real site with a chat, you keep building.
How to let a client edit a site you built with Cursor
A site built in Cursor is code in a repository. Connect that repository on GitHub to Siteshare and your client edits the real site with a chat.
How to let a client edit a site you built with Lovable
Sync the Lovable project to GitHub, host it from there, and connect it to Siteshare. Your client edits without access to your Lovable workspace.
How to let a client edit a site you built with Codex
Codex works on your GitHub repository. Connect that repository to Siteshare and your client edits the real site with a chat, while Codex keeps opening PRs.
How to let a client edit a site you built with v0
Connect the v0 project to GitHub and to Siteshare. Your client edits the real Next.js site without a v0 seat, and Vercel builds what they publish.
How to let a client edit a site you built with Bolt
Sync the Bolt project to GitHub, host it from there, and connect it to Siteshare. Your client edits without a Bolt account or your tokens.
Per framework, without a CMS
Let clients edit a Next.js site without a CMS
Your client changes texts and images in a Next.js site where they are, in JSX or MDX. No schema, no headless CMS, and route handlers stay yours.
Let clients edit an Astro site without a CMS
Your client edits the real Astro site: texts in .astro pages and components, and entries in content collections. No CMS, no schema to describe twice.
Let clients edit a SvelteKit site without a CMS
Your client edits texts in +page.svelte files and components on the real site. Server files, hooks and settings stay protected by default.
Let clients edit a Nuxt site without a CMS
Your client edits the real Nuxt site: texts in .vue pages and components, and Markdown in Nuxt Content. The server/ folder stays yours.
Let clients edit an Eleventy site without a CMS
Your client edits the Markdown and templates of an Eleventy site on the real site, with drafts and a build check. No Decap config to write.
Let clients edit a Hugo site without a CMS
Your client edits the Markdown in content/ of a Hugo site on the real site, with drafts and a build check. A theme in themes/ works; Hugo Modules don't yet.
Let clients edit a plain HTML site without a CMS
A site of plain HTML files can't have a CMS without a rebuild. With Siteshare your client edits the HTML itself, with drafts and your approval for scripts.
Hosted where it is now
Cloudflare + Siteshare
Keep the site on Cloudflare. Your client edits it in Siteshare, and Publish is one commit on main that Cloudflare builds and takes live.
Netlify + Siteshare
Keep the site on Netlify. Your client edits it in Siteshare, and Publish is one commit on main that Netlify builds and takes live, without a Netlify seat.
Vercel + Siteshare
Keep the site on Vercel. Your client edits it in Siteshare without a Vercel seat or a headless CMS, and Publish is one commit on main that Vercel deploys.
Hand it over. Get your evenings back.
Free for one site, forever. No card needed.