ContentKit

ContentKit bridges the gap between developer blogs (markdown in a repo) and enterprise CMS platforms (WordPress, Ghost). It gives content editors a visual editing interface through Sanity Studio while keeping the frontend a fast, type-safe SvelteKit app.

The Sanity integration goes deeper than most tutorials show. Draft previews render unpublished content in a side-by-side view. Scheduled publishing sets a future publish date and automatically triggers a Vercel rebuild. Content relations (categories, tags, authors) are all structured and queryable.

What stands out

The editorial workflow. Editors get a proper writing environment — rich text, image uploads, drag-and-drop block reordering, and inline previews. They can save drafts, request reviews, and schedule publications without touching code or understanding Git.

GROQ queries (Sanity’s query language) are type-safe throughout. The starter generates TypeScript types from your Sanity schema, so content queries in your SvelteKit load functions catch type errors at build time.

Where it could improve

Sanity’s free tier includes 100K API requests/month and 500MB of assets. For a popular blog, you’ll hit those limits within months. The paid plan ($99/month for the Team tier) changes the economics significantly — budget for it.

The ISR (Incremental Static Regeneration) setup is tightly coupled to Vercel. If you want to deploy to Cloudflare Pages or Netlify, you’ll need to rework the revalidation strategy. A more portable approach would strengthen this starter.