You are right with Jekyll, but quite on the wrong street with GitHub pages. It takes time to get your changes up and running, I would say that'd be around ~15 minutes, and I believe that depends on worker's availability on the GitHub server to "compile" or "render" your Jekyll blog.
My experience currently is with Hugo. I have a DigitalOcean (DO) VPS that I use to host my Hugo blog.
The workflow is as follows:
1. Commit and push from local to my VPS.
2. My VPS receives the commit, a git hook runs server-side build for my Hugo blog. The script is pretty short.
3. Server finishes build process, new changes are reflected.
Feel free to experiment with that others are suggesting here, e.g. Netlify. Jsyk, I pay $5/month for my DO VPS and that is $0.50 cheaper than my everyday coffee.
My experience currently is with Hugo. I have a DigitalOcean (DO) VPS that I use to host my Hugo blog.
The workflow is as follows:
1. Commit and push from local to my VPS.
2. My VPS receives the commit, a git hook runs server-side build for my Hugo blog. The script is pretty short.
3. Server finishes build process, new changes are reflected.
Feel free to experiment with that others are suggesting here, e.g. Netlify. Jsyk, I pay $5/month for my DO VPS and that is $0.50 cheaper than my everyday coffee.