Hello, Studio

If you've heard of Sanity, it's likely that you think of it as a CMS. It can be that, but it is also so much more. We believe in modeling content as data—not its presentation—and giving developers tools to create great content experiences for authoring teams.

Sanity provides a hosted backend for your text content and assets called the Content Lake. Within the Content Lake, you must create a project and a dataset

• A dataset is a collection of content within a project hosted in Sanity. See Store and query structured content for more.
• A project can have many datasets and also contains project-level settings like members and API tokens. You can see these in sanity.io/manage.
• An organization can have many projects which you would colocate for billing and administration purposes. Most companies using Sanity only have one "organization," but an agency may make a unique organization for each client.

Locally, you will configure Sanity Studio with TypeScript. Think of it like a "headless CMS," "admin panel" or "content dashboard" which is configured with code but reads from and writes to the Content Lake in real-time.

In this course, you will deploy the Studio to Sanity's provided hosting, but know that you can host it with most web hosting providers.

The command below will create a new project and dataset within the content lake and scaffold the local files required to develop Sanity Studio.

pnpm create sanity@latest --template clean --create-project "Day One Content Operations" --dataset production --typescript --output-path day-one/apps/studio

This command set this path so that the Studio would be installed in an apps directory. Eventually in this track you'll create a front-end, Sanity Functions and a custom content application which will all be colocated in this apps directory.

The folder structure created in the command above should look like this:

day-one/
└── apps/
    └── studio/ <- Sanity Studio

With a Studio installed, let's get it running in the next lesson.