Closed janosh closed 1 year ago
@janosh why exactly do we need this? or is this just some side-project / technical gimmick?
One less 3rd party is the main selling point. New maintainers will only have to signup to GitHub, no need to signup to netlify and get familiar with another platform. Also, build times are ~3-5x faster.
@janosh oh cool, so this should replace netfliy? awesome! let me know if one can help you with this.
Yes, GitHub Pages could be our Netlify replacement. The only outstanding problem I see (which is why I didn't merge yet) is how to deploy multiple pages for i18n. In Netlify, we currently have separate sites for each new languages. This might not be the ideal setup to manage multiple languages. But if we keep it for now, would require more setup here.
Using 1st party
deploy-pages
action currently in public beta.