deploy previews

[gerbrent]

Discussed in https://github.com/JupiterBroadcasting/jupiterbroadcasting.com/discussions/182

^{Originally posted by elreydetoda July 24, 2022} So, one thing that I've normally done in the past is hooked up Netlify to the repo. Normally this is for easy of hosting the NetlifyCMS, but a passive added benefit is using them for deploy previews. This means it'll automatically deploy the changes proposed in a PR for the website. It can be used on the free tier and if layer down the road it breaks or cost money. It'll be easy to remove it, and we'll go back to doing what we're currently doing.

So, this is an example past website that has a deploy preview: https://github.com/Climate-Refugee-Stories/crs-website/pull/95

Then this is the config that's used: https://github.com/Climate-Refugee-Stories/crs-website/blob/master/netlify.toml

It'll take someone on the JB side to hook it up (I'd be willing to hop on a call and work through it with them), but it'd be nice to see peoples change and interact with them instead of relying on people sending screenshots. 😅

There are more advanced features which you'd have to pay for, i.e. a utility overplayed on the website for screenshot'ing + commenting while you're navigating the deploy preview, but just the actual deploy preview feature is free.

We could eventually hook everything up to do deploy previews based on where the changes were coming from but till then just the JB.net works.