Central storage and serving of static assets consumed by Songwhip.

- Mostly used for referencing video content from Prismic (out CMS for marketing pages).
- We keep these static assets decoupled from deployments as Prismic publishes are not tied to `songwhip-web` source-control.
- Can be used if images/logos need to be referenced from email, although it's probably better to serve these from `songwhip-images` or expose a static endpoint from `songwhip-email` or whatever project the email content resides.
- Vercel handles global serving/caches from the edge so performance is great.

## Workflow

1. Add an asset to this repo
2. Open PR and merge
3. Wait for Github Actions to publish a new deployment

> You can also push your branch to `staging` if you want to test your changes before merging to master/production. Content on the `staging` branch is served at `static-staging.songwhip.com`.