# Changelog, January 2025: the foundations

Turbo Start Sanity began as a Turborepo with a Next.js app and a Sanity Studio side by side. Here is what the first month put in place.

![Neon yellow and orange light streaks crossing a dark dotted grid](https://cdn.sanity.io/images/s6kuy1ts/production/57efbed4ccc2c41cd2bb2821848afe69b12edd57-4096x2596.png?w=1600&fm=webp&q=80&auto=format)

Every starter makes the same promise: skip the boring setup. January was about earning that. A monorepo, a Studio, a frontend and a handful of decisions you would otherwise make at 11pm on day one.

## One repo, two apps

The project landed as a Turborepo with the Next.js frontend and the Sanity Studio living next to each other. Shared tooling, one install, one place to run everything. You stop syncing two repos by hand, and changes to schema and frontend ship in the same pull request.

## Common schema types from day one

Reusable schema definitions arrived in the first commits, so documents share the same building blocks instead of re-declaring fields. Later in the month a settings schema joined them, giving you one place for site-wide values rather than hard-coding them in components.

## Name tokens for what they do

The Sanity API token was renamed to `SANITY_API_WRITE_TOKEN`. A small change, but the name now tells you exactly how much power it holds. It does not belong anywhere near the browser.

Boring foundations, laid early. That is the whole point of a starter.