Let clients edit their website, safely
ComingNot live yet: the Preview buttons, approval and publishing.
Your Client's Website, Edited In Place
Click-to-edit is coming. Clients will click the words that need changing and type, and Sitehand will trace each edit to its content file and add it to a change for review. Editing on a preview follows once Sitehand can show one.
ComingNot live yet: click-to-edit on a preview.
From Repository To Published Change
Connect your repository and Sitehand reads your site. Setup from the app, copy conversion and publishing will follow.
- 1
Connect your repository
Install the Sitehand GitHub App and tell Sitehand which repository holds your site.
- 2
Sitehand reads your site
Sitehand reads the repository and reports the framework, the content it found, and anything it can't edit yet. Nothing is written.
- 3Coming
Choose what's editable
Review the proposed setup. Sitehand puts it on a branch. You open the pull request on GitHub and merge it.
Coming: setup from the app is waiting on its final proof run.
- 4OptionalComing
Make hard-coded copy editable
If your words live inside components, Sitehand can propose a branch that moves them into content files. You review it and merge it.
Coming: copy conversion is built and in testing. It opens once it runs on hosted servers.
- 5Coming
Make your first change
Edit a page, send it for review, and publish. Your host deploys it as usual.
Coming: publishing waits on build checks from Vercel.
Edits Your Clients Can Make Alone
Sitehand reads your site's content files and turns them into simple forms, so clients change words, prices and images without touching code.
Supported Content Collections Become Forms.
Supported content collections become forms. YAML stays read-only. Collections loaded from an API or a CMS aren't supported. Once previews arrive, Vercel will build each change so clients see the real page before anyone approves it.
Forms From Your Schema
Fields, types and limits come from the site itself.
Preview Of Each Change
Vercel will build a preview deployment of each change.
A State For Every Change
Each change shows where it stands, from the first edit to review.
ComingNot live yet: the preview, the build check, and the Approved and Live steps.
Click The Words. Type The Fix.
Clients will click the sentence that is wrong and correct it in place. Sitehand traces the text back to the file it came from and adds it to a change. Click-to-edit on a preview is coming, and needs a preview Sitehand can show.
Edit In Context
Text changes happen on the page people actually see.
Traced To Source
Each edit lands in the right content file, nowhere else.
Same Safety Net
In-place edits go through the same review as any other change.
Every piece is built by hand in our Cornish workshop from sustainably felled oak and ash.
We started in 2011 with one bench and a borrowed lathe. Today a team of nine makes around four hundred pieces a year.
Not live yet: click-to-edit on a preview.
All Your Client Sites At A Glance.
See which sites have changes in progress and which changes are waiting for review.
Portfolio View
Status and changes in progress for every site.
Roles Per Site
Editors, approvers and admins, set once.
Connect From GitHub
Install the GitHub App and name the repository.
Sites
Connect site2 changes in progress, 1 waiting for approval.Last publish by Priya Shah.
No changes in progress, 2 waiting for approval.Last publish by Tom Reyes.
4 changes in progress.Last publish by Ana Lima.
1 changes in progress.
Not live yet: the Preview buttons, approval and publishing.
Every Change Goes To Review
Changes go to review. Approval and publishing are coming, with previews, build checks, rollback and Slack.
Approve Changes Without Leaving Slack.
Slack approvals need Sitehand hosted at a public address and build checks from Vercel. Once both land, each change ready for review will appear in the client's channel with its build result and a link to it.
Ready-To-Review Alerts
One message per change, in the channel you pick.
Approve Or Reject Inline
Buttons that respect each person's role. Approve will appear once the build passes.
Thread Stays In Sync
The message updates as the change moves on.
ComingNot live yet: Slack, build results, previews and approval.
Every Change Recorded.
Sitehand keeps the full record of who made each change and when it went to review. Approval, publishing and rollback from History arrive with Vercel build checks.
Release Timeline
Will list publishes and rollbacks with the exact commit.
Audit Log
Every action, by every person, on every channel.
Rollback
Will restore a previous release without a developer.
History
Northwind DentalNot live yet: build checks, approval, publishing, rollback, and changes from Slack or Claude.
Your Rules Run On Every Change.
Clients can only touch content, never code. Required approval and holding a release until the site builds arrive with Vercel build checks.
Required Approval
An approver will sign off before anything goes live.
Build Check
A broken build will never reach the live site.
Writable Roots
Edits are limited to the content folders you allow.
Not live yet: approval, build checks, Slack alerts and agent rules.
Ask For Changes Anywhere.
Clients edit by hand today. Asking Claude and handing a request to the agent will follow. Every route ends in the same reviewed change.
Ask Claude. Get A Reviewed Change.
The Claude connector needs Sitehand hosted at a public address. Then clients will ask Claude for a change in plain words, and Claude will make it through Sitehand for review.
Plain-Language Requests
“Raise the Family plan to £24” is enough.
Same Permissions
Claude acts as the person, with their role.
ComingNot live yet: the Claude connector, previews and approval.
Hand Over The Fiddly Jobs.
The agent lane needs a hosted sandbox, which waits on our hosting tests. Then, for changes that span many files, the agent will work through the request step by step and send the change for review.
Sandboxed Work
Writes stay inside the allowed content folders.
Visible Steps
Every tool call is listed as it happens.
Metered Budget
A spending cap per run and per month.
Agent run
Running · 1m 12sCancelNot live yet: the agent lane.
Every Route Ends In The Same Review.
Every change goes through the same review and lands in the same history. Today changes start on the web. Click-to-edit, Slack, Claude and the agent will follow.
One Queue
Every change, whatever started it.
Site Overview
Open changes and recent activity for each site.
Same Approval Rules
Every route goes through the same review.
Not live yet: approval, publishing, rollback, and changes from Slack, Claude, click-to-edit or the agent.
One Platform. Every Client Site Covered.
Simple pricing for agencies and in-house teams. No per-editor fees. No surprise overages.
ComingFeatures marked * are not live yet.