v3 does what v2 don't - Sanity.io Meetup
How to run the demos locally
bookmarks.studio
Async config demo
cd 010 && npm i
cp .env.example .env.development
and modify.env.development
with your own Sanity projectnpm run sanity:dev
Nextjs config demo
Live bookmarks.studio
cd 010 && npm i
cp .env.example .env
and modify.env
with your own Sanity projectnpm run dev
getstarted.lol
Use the Deploy button to end up with a working instance of the demo:
This demo only works if you're logged in to the studio, it doesn't pair with the unstable_noAuthBoundary
API that the other demos are using.
sanity.parts
This demo shows how one Studio instance: https://sanity.parts/blog/desk
Is reused and deployed on two other sites:
You can start by deploying your own:
npm i && npm run build:vX
- Push the commit to trigger a new vercel deploy.
- Make a new site, somewhere, and paste a snippet like this:
<div id="sanity"></div> <script type="module"> import { createStudio } from 'https://projectId.sanity-parts.vercel.app/vX/blog.js' createStudio(document.querySelector('#sanity'), { projectId: 'projectId', dataset: 'production', title: 'Sanity Studio', }) </script>
- Now, whenever you run
npm run build:vX
and push all the Studios using it will update😉