Description
Currently, you need to have Sanity API access to contribute to site. This is not ideal for open source development.
Suggested solution
Whenever there's a build, also provide an archive of the most recent pull from Sanity and make it available, maybe as a release, and add a codepath to allows https://github.com/chromeos/chromeos.dev/blob/main/site/lib/sanity.ts to switch to use that archive instead.
Alternative
No response
Additional context
No response
Validations
### Tasks
- [x] Create archive of Sanity data dump
- [ ] Create an archive of images when a flag is passed into the build
- [ ] Redirect images to local copy on `dev:offline`
- [ ] Make content and image archive available in a release people can download
Description
Currently, you need to have Sanity API access to contribute to
site. This is not ideal for open source development.Suggested solution
Whenever there's a build, also provide an archive of the most recent pull from Sanity and make it available, maybe as a release, and add a codepath to allows https://github.com/chromeos/chromeos.dev/blob/main/site/lib/sanity.ts to switch to use that archive instead.
Alternative
No response
Additional context
No response
Validations
#chromeosor#chromeos-forumchannels in the Google Developer Community Discord.