How to implement Handover on your client site
Follow these guides to connect API keys, embed editable content, set up /admin, and launch with lock-state protection. Focused on what to do, in order.
- 1
pnpm create handover@latest my-client-site - 2
cp .env.example .env.local - 3
Set NEXT_PUBLIC_HANDOVER_API_URL and NEXT_PUBLIC_HANDOVER_API_KEY - 4
pnpm dev
Exact implementation sequence from API key to live edits.
Clear /admin setup path for non-technical client users.
Lock-state and error handling patterns you can ship with confidence.
Core guides
Start here to integrate Handover into your pages and admin workflows.
Create your first project, connect API key, and verify editing + lock flow.
Wire editable text and images into your site with stable keys and fallbacks.
Implement /admin login and editing actions for non-technical client users.
Map SDK error codes to clear UX states and safe fallback behavior.
Docs index
Full implementation index for setup, embedding, admin, lock behavior, and go-live operations.
Quickstart
Getting started with Handover
Create your first project, connect a site with the API key, and verify your client can edit safely from /admin.
Implementation
Embed editable text and image fields
Implement editable regions in your site so client content is rendered from Handover and updated without redeploys.
Implementation
Implement the client admin area
Set up /admin login and editing flows so clients can update content safely without direct code or infrastructure access.
Reliability
Handle lock state and SDK errors
Map Handover error codes to clear UI states so clients and teams always understand what happened and what to do next.