Repository structure about hackyourfuture.be HOT 3 CLOSED

Good morning @jbelien, thanks for the issue! Right now the site (deployment-wise) is in ugly keep-it-working mode so it can be live when we submit the DBSF proposal. For this quick fix it's in the repsitory called hyfbe.gh.io given how github pages works and that we want the module pages to stay live (ie. hackyourfuture.be/encapsulation)

Michiel will be helping me find a better solution, we'll move the code to a new repository and deploy through Netlify. At that point I'll document the arrangement in the repo.

And about the branch naming, I wanted to use gh-pages but the username.github.io repositories can only be deployed from master thus the dev branch gymnastics. Just learned this Friday while trying to use the gh-pages branch. When we move the code back to the /website we'll also switch to better branch naming

from hackyourfuture.be.

• dev branch renamed to main
• main branch deployed on Netlfiy: https://hackyourfuturebe.netlify.app/
• Deleted GitHub Actions that deployed on GitHub Pages
• Delete master branch when https://hackyourfuture.be/ is pointing to Netlify
• Delete HackYourFutureBelgium/website-temp repository when we are sure everything is working fine
• Create a develop branch: every push to main branch will be deployed on Netlify ; a develop branch allows you to push with deploying it
• Write proper README file (it was still the default Gatsby README file)
• Keep the libraries up-to-date: I enabled Dependabot on the repository ; it will send automatic Pull Request every month with the last version of the libraries

from hackyourfuture.be.

To simplify the deployment (and avoid depending on Netlify), I have setup the deployment here on GitHub Pages using GitHub Actions (see deploy.yml)

from hackyourfuture.be.