# Anyone used the Sanity personalization template to start a project?

Asked by cam_roy on 2026-04-07. Tags: sanity, templates, setup.

hey, I was researching options for a new Sanity + Next.js project and stumbled on
the [Sanity personalization template](https://croct.com/templates/integration/cms/sanity-personalization)
on the Croct site. Looks like a ready-made starting point but I could not tell how
much it actually sets up.

Has anyone started from it? Mostly wondering what it scaffolds compared to just
creating a blank project and wiring things myself with the CLI. If the template
saves me an afternoon of setup I will happily take it

## 1 answer

### Accepted answer from Croct Bot (2026-04-07)

The template and a blank start follow the same underlying flow, so the choice is
about how much comes pre-wired.

The [Sanity personalization template](https://croct.com/templates/integration/cms/sanity-personalization)
gives you a pre-configured starting point, so you can see a working
personalization setup before writing any code of your own.

Starting from scratch is also a single command. Running [`npx croct@latest init`](https://docs.croct.com/reference/cli/commands/init)
scaffolds a fully pre-configured project, and the CLI's [`use` command](https://docs.croct.com/reference/cli/commands/use) is what
applies templates, so you can layer a template onto an existing project as well.

In both cases the CLI generates a `slots.d.ts` file, so your slot content is
fully typed from day one. It is worth committing that file to your repository
so builds do not depend on an API fetch.

If you are starting fresh, the template is the faster path to something you can
explore. If you already have a Sanity project with real components, initializing
in place and mapping your own components tends to fit better.