My implementation biases towards GitHub Pages because it doesn't require any external service signup. But it's worth noticing that other options like Vercel and Netflify would be an easier solve in regards to the above issues, since they do not have the issue with non-root publish URL. For a template project, there are still good reasons to prefer GitHub Pages - but if anyone wants a near-term solve, the other providers would likely have fewer sharp edges.
This isn't a priority, per se, but I just want to log that one nice feature is the ability to publish the Evidence report as a static webpage.
I have an example published from the MeltanoLabs fork here:
There's an outstanding bug - only affecting subpages, and only from non-root URLs - and it looks like this mat be fixed in a future Evidence release:
My PR from the fork is here (https://github.com/MeltanoLabs/jaffle-shop-template/pull/5), and I updated that PR with some post-merge learnings and action items:
Note
My implementation biases towards GitHub Pages because it doesn't require any external service signup. But it's worth noticing that other options like Vercel and Netflify would be an easier solve in regards to the above issues, since they do not have the issue with non-root publish URL. For a template project, there are still good reasons to prefer GitHub Pages - but if anyone wants a near-term solve, the other providers would likely have fewer sharp edges.