How I built Sane Kit

Sane Kit started like most side projects: a personal itch. I was tired of wasting hours wiring together the same boilerplate just to test a content idea. Headless CMS here, frontend config there, half a dozen tabs open, and before writing a single line of content, I was already mentally exhausted.

I wanted something that felt like a launchpad — not a framework, not a boilerplate dump, but a clean slate with just the right decisions made. No tech bloat, no architecture astronautics. Just modern tooling, connected and ready.

The Stack

Sane Kit is built with Next.js 15, using the App Router for its simplicity and performance benefits. I paired it with Sanity.io for content management — mostly because of the Studio's flexibility and real-time editing experience.

The project is divided into two apps:

• /web – the frontend, built with Next.js + Tailwind + Shadcn/UI.
• /studio – the Sanity Studio, configured locally but ready for deployment.

Features

• Minimal but powerful content types: Page, Post, Settings.
• Built-in blog system with example posts and reusable layouts.
• Component-driven design using server components.
• Visual editing with Sanity's Presentation tool.
• Seamless deployment to Vercel or your preferred host.
• Easily extendable schema and modular file structure.
• Pre-built UI blocks with TWBlocks — huge time saver!

Why TWBlocks Helped

Designing from scratch every time gets old. TWBlocks gave me flexible, copy-pasteable Tailwind components I could drop in, tweak, and keep moving. Combined with Shadcn, it made the UI clean and coherent without fuss.

Final Thoughts

Sane Kit is not a framework.™ It’s a focused starter. Like a bonsai — lightly maintained, trimmed just enough to stay elegant. I built it to ship ideas fast, and if it helps you do the same, that’s mission complete.