I just found a better solution related to issue #1
We can utilize this gatsby plugin to use GitHub GraphQL API directly as our data source. This solution is way better than hardcoding every project's data into a JSON file. So, every time there are new changes to a repository data (issues, forks, etc.), the maintainers just need to rebuild and redeploy the site (since Gatsby generates static pages files at build time).
I'm not familiar with Github pages, but in Netlify, we can automate the rebuild process by utilizing the Build hooks feature so the build and deploy process will work seamlessly.
pic related
I just found a better solution related to issue #1
We can utilize this gatsby plugin to use GitHub GraphQL API directly as our data source. This solution is way better than hardcoding every project's data into a JSON file. So, every time there are new changes to a repository data (issues, forks, etc.), the maintainers just need to rebuild and redeploy the site (since Gatsby generates static pages files at build time).
I'm not familiar with Github pages, but in Netlify, we can automate the rebuild process by utilizing the Build hooks feature so the build and deploy process will work seamlessly.
pic related
