Projects · Client Site Starter
Live demoJed.
One clone, one client, ready to ship.
A production-ready base for branded client websites, built on TanStack Start and Supabase. Each client gets a fresh clone with sign-in, an admin panel, a blog, a contact inbox, and an API and MCP server already working. It was first used to rebuild a church website.
Setup
One clone per client
Access
REST API + MCP
Admin
Blog, pages, inbox


Starter homepage · Role: Creator & Lead Developer
Inside
What ships in the box
- jed-starter.vercel.app/public-homepage

public-homepage
Public site
Homepage, docs and blog with Ctrl K search, a sitemap and a rate-limited contact form.
- jed-starter.vercel.app/admin-dashboard

admin-dashboard
Admin dashboard
Dashboard for drafts, inbox, media, and recent activity so operators see what needs attention.
- jed-starter.vercel.app/settings-branding

settings-branding
Settings and branding
Set the logo, accent colour and layout widths so each clone looks like its client.
- jed-starter.vercel.app/api-tokens

api-tokens
API and MCP tokens
Scoped tokens for the REST API and MCP. Writes need a confirm step and an idempotency key.
- jed-starter.vercel.app/two-step-login

two-step-login
Sign-in and two-step login
Email or Google sign-in, with authenticator app codes that admins can require by role.
Highlights
Built for client handoff
- Pages and blog drafts in a block editor, with media, redirects and RSS
- Roles enforced by row-level security, with optional or required two-step login
- One personal access token works for both the REST API and MCP
- Every API call runs as the token owner and lands in the audit log
One clone, one client, ready to ship.
Live demo