Decided once. Committed.

The Sanity setup you stop rebuilding.

Common problems
001 Page builder schema + section registration + preview ~5 HRS. 002 Draft mode + live preview + webhook revalidation ~4 HRS. 003 CDN vs. data cache — stale content after publish ~3 HRS. 004 Studio structure editors can actually use ~3 HRS. 005 SEO metadata, OG images, sitemaps, robots.txt ~2 HRS. 006 Rewriting the same 12 components ~2 HRS. 007 Redirects, analytics, view transitions, Mux ~2 HRS. 008 Contact form + spam guard + Resend wiring ~1 HR. 009 ESLint, Prettier, Biome, git hooks ~1 HR. 010 Basic auth for staging environments ~1 HR. ESTIMATED TIME LOST: ~24 HOURS PER PROJECT (3 FULL DAYS)

The page builder alone costs you days. Every single time.

Every decision already made. So you can skip to the actual work.

  • 001 / Schema as a system

    Document roles, factory functions, singletons. Every schema looks the same, so every editor knows where to go. You never model the structure from scratch again.

  • 002 / The hard fields, already built

    The three fields nobody gets right the first time. A link field that handles internal refs, external URLs, email, and params. A media field that normalizes image, Mux, Rive, and Lottie into one shape, each returning dimensions, so you forget layout shift. A page builder with guardrails. Reusable, typed, composed everywhere.

  • 003 / Agent-native

    Ask an agent to build this and you get a different architecture every run, all plausible, none decided. Here the decisions are made. AGENTS.md and a dozen scoped skills let any agentic tool ingest the conventions instead of inventing them, and preconfigured MCP servers let it read the Next.js runtime and drive a real Chrome to check its own work. No drift.

  • 004 / Fetch layer, solved

    CDN bypassed in production, Data Cache doing the work, webhooks invalidating on publish, draft mode wired in. Stale content after publish stops being a midnight problem.

  • 005 / A Studio editors actually use

    Every document type where editors expect it. Pages own their routes, singletons stay locked, no hunting. Clients stop emailing to ask where their homepage lives.

  • 006 / SEO, done not deferred

    Per-page metadata from schema, sitemap driven by Sanity, OpenGraph with auto-cropped images, robots.txt included. Nothing bolted on the week before launch.

  • 007 / Production-ready from day one

    Basic auth, spam-protected forms, redirects managed in Sanity, analytics, view transitions. The plumbing you reconfigure every project, already wired.

  • 008 / Wired up, not just cloned

    An interactive setup script provisions the Sanity project, mints the tokens, adds CORS, and registers the revalidation webhook, then writes your .env. Export and migration scripts back up production and move content between environments. The first run is handled, not documented.

This is the actual repo.
README.md
Terminal
~/the-content-architecture > get-access # €399 · one-time · ENDS JUL 16
~/the-content-architecture > 
mainUpdated today

The work that gets remembered.

Good Fella

House of Honey

Aspen Search

Anuc Home

Edoardo Lunardi

Serve Robotics

Muralia

blink

WASL

Creative Lives in Progress

This site :D

“We shipped the Good Fella site on an early version and it saved us tons of time. Six months in, we're still building pages and sections in an afternoon without fighting the setup.”

Julian Fella

Co-Founder, Good Fella

“Edo and I ran a client project on this together. The plumbing was already handled, so the week we'd normally lose to setup went into the creative work the client actually remembers.”

Elliott Mangham

Founder & Frontend Engineer

“I opened the fetch layer and found the revalidation problem I'd burned two days on last project, already solved and committed. That one folder paid for the whole thing, and the rest is six years of decisions I'd have made the slow way.”

Malik Kotb

Web Designer & Engineer

01/03

Slide 1 of 3

One repo. One pricing. Lifetime updates.

€399
€549
LAUNCH OFFER · ENDS JUL 16
  • 001ONE-TIME FEE, NO SUBSCRIPTION
  • 002PERPETUAL LICENSE, UNLIMITED PROJECTS
  • 003COMMERCIAL USE, NO ATTRIBUTION
  • 004LIFETIME UPDATES, INCLUDED
  • 005PRIVATE GITHUB DISCUSSIONS
  • 006DIRECT LINE TO THE MAINTAINER
  • 007FULL SOURCE ON PURCHASE, SALES FINAL
  • 008FOR NEXT.JS + SANITY ENGINEERS, NOT NO-CODE
  • 009ALL PRICES IN EUR
Getaccess

Before you buy

Getaccess

  • Next.js 16 with the App Router and React Compiler, Sanity v6, TypeScript in strict mode, Tailwind 4, and Biome for lint and format. Deploys on Vercel out of the box, and runs on Cloudflare via OpenNext.

  • No. The opinion lives in the architecture, and the tools sit on top of it. Tailwind, Biome, Mux, Rive, Lottie, these are the defaults I reach for on most projects, wired in cleanly so they come out just as cleanly. Don't want Tailwind? Pull it. Prefer ESLint over Biome? Swap it. No Mux, Rive, or Lottie in this project? Drop them. What you are really buying is the patterns underneath, how content is modeled, fetched, and composed. The libraries are just what I ship with on 90% of my projects.
    The Sanity layer is decoupled by design too. Every import inside the sanity/ folder is relative or an external package, nothing reaches into the Next.js app, so you can lift the whole Studio, schema, and field primitives into another project. The content layer doesn't hold you hostage to the front end.

  • Some, yes. This is a real codebase, not a no-code template. You should be comfortable in a Sanity schema file and a Next.js project. If you are, you will feel at home in minutes. If you have never opened a schema, the article series is the best place to start before deciding.

  • No, and I'd rather tell you here than take your money. This is a real Next.js and Sanity codebase, not a no-code tool: no visual page builder, no drag-and-drop editor. You clone the repo and write real code on top of it. If you don't work in Next.js and Sanity, it isn't for you.

  • Yes. Unlimited projects, commercial use, no attribution required. Use it on every client site you ship. The one thing you cannot do is resell the architecture itself as a competing product.

  • Most boilerplates give you a pile of features. This gives you decisions. Every hard call, document modeling, the fetch layer, revalidation, the link and media fields, was made once over six years and committed. It is opinionated on purpose, and it is the architecture I ship my own client work on, not a side project cleaned up for sale.

  • A free starter gets you a clean install and the easy parts. What it leaves you is the work that actually costs the days: a page builder with guardrails, the fetch layer and revalidation, the link and media fields, a Studio structure your editors don't email you about. Those decisions are still yours to make on every project. Here they're already made, over six years of real client work, and committed. You're not paying for code you could scaffold in an afternoon. You're paying to skip the part nobody quotes for.

  • It is built for it. AGENTS.md plus a dozen scoped skills mean any agentic tool ingests the conventions and boundaries before you write a prompt. Ask an agent to build this from scratch and you get a different architecture every run. Here the decisions are already made, so the agent works inside them instead of inventing new ones. You still read and write the real code yourself; the agent works inside the architecture, it does not write the app for you.
    It also ships two preconfigured MCP servers. One reads the running Next.js dev server: compilation errors, routes, docs that match the installed version. The other drives a real Chrome: screenshots across viewports, performance traces, screencasts of transitions it can review frame by frame. The agent doesn't just know the conventions, it can look at the app it's changing.

  • This is my daily driver, so I keep it current. Next.js majors, Sanity migrations, breaking plugin changes, I handle them and push the update. Your license includes every update for as long as I maintain it, which is for as long as I am using it myself.

  • The full repo on day one, a perpetual license, and lifetime updates included, not sold as a separate tier. One payment, no subscription. You own it forever.

  • Buyers get a private GitHub Discussions space, threaded and searchable, where I answer questions directly. For anything bigger, I am reachable by email. What you will not find is a Discord to get lost in or a support queue that routes you to a bot.

  • Tell me, and it gets fixed in the codebase, usually fast. A bug you hit is a bug my own client projects will hit too, so fixing it is in my interest as much as yours. The patch ships to everyone.

  • Because you get the full source on purchase, sales are final, the same way every serious code product works. Once the repo is cloned, it cannot be un-cloned. So I have put everything you need to decide up front: read the article series for the full reasoning, browse the real repo above, and look at the sites already shipped on it. If something is unclear before you buy, email me and I will answer honestly, sometimes that means telling you it is not the right fit.

  • It is a set of architectural decisions, made once over six years and committed, that gets you to the real work faster. You write real code on top of it. There is no no-code editor, no UI kit or component library to theme, no auth-billing-dashboard SaaS scaffolding, and no course wrapped around it, though the article series explains the reasoning behind it. You buy it once and own it.
The content architecture