A single repository containing both the Sanity studio and NextJS front-end code. Both directories have their own README with more information about their respective setups.
Thus far I've been opening 2 side-by-side terminals in VSCode, then running npm install and npm run dev in both. Ensure you create .env files in /next and /sanity that match each directory's .env.EXAMPLE. For the Next .env file you'll need a read token you create in your project API settings at sanity.io/manage.
The 4 directories that make up this project are:
.
├── .github/workflows
├── .vscode
├── example-data
├── next
├── sanity
└── .nvmrc
The /next and /sanity directories each have their own README files that describe those projects more in depth.
Home for YAML configuration files that trigger GitHub Actions.
Deploys the Sanity Studio when changes are pushed to the /sanity directory on the main branch.
If you want to use this action you need to add secrets from ./sanity/.env to GitHub for the Studio to build.
A settings.json file for linting and formatting on save. Feel free to delete/modify to match the Schwab team's preferences.
The JSON objects that were sent to us as examples of the content types being built
A NextJS 14 app leveraging RSCs and wired up to the Sanity Content Lake
The Sanity Studio for this POC.
Node version used to bootstrap project (18)