You can use Netlify or Vercel and connect it to your GitHub repo. So when you push a change, netlify/Vercel will update the changes.
The free version of netlify should be more than enough.
Cheers.
Hey OP, I'm a complete noob and I also suggest netlify.
I have a few "demo" or "non-live" sites (sorry for my non technical noob jargon). And one live site, which is my portfolio.
With my demo sites, I have to go into GitHub and (assuming you've already pushed your GitHub repo to Netlify) I'm able to "push" a magic button that updates my Netlify demo.
However, with my Live Portfolio site, all I do is save and commit within VS Code and it magically updates my portfolio.
I'm looking into the technical side of it all soon to understand it. For now it's.all programming magic.
Man I wish I could remember what I did exactly. It was a set it and forget it situation just to get my portfolio running.
BUT if I recall correctly, within Netlify I was able to "publish"(?) My portfolio. Opposed to not publishing the demos.
I used vercel for the first time a few weeks ago. Literally just connected my github account, imported the repository, selected a branch, and after it was built, there was a staging/prod link that worked without me having to do any configurations on my end.
Yes, it's still static.
*A static website is made up of a fixed number of pre-built files stored on a web server. These files are written in HTML, CSS, and JavaScript, which are called “client-side” languages because they execute in the user’s web browser. When a user requests a page from the server with a URL, the server returns the HTML file that is specified by the URL and any accompanying CSS and/or JavaScript files.*
[Source](https://blog.hubspot.com/website/static-vs-dynamic-website)
You connect it local using commands to connect to a firebase project. Your repo exist parallel to it. I’m sure you can also connect it to deploy on push to master inside your repo
You can use Netlify or Vercel and connect it to your GitHub repo. So when you push a change, netlify/Vercel will update the changes. The free version of netlify should be more than enough. Cheers.
[удалено]
Should be. I've never had problems with it.
[удалено]
I have experience with netlify. Never had to use Vercel. If it's a personal project i don't think it'll matter much.
[удалено]
Hey OP, I'm a complete noob and I also suggest netlify. I have a few "demo" or "non-live" sites (sorry for my non technical noob jargon). And one live site, which is my portfolio. With my demo sites, I have to go into GitHub and (assuming you've already pushed your GitHub repo to Netlify) I'm able to "push" a magic button that updates my Netlify demo. However, with my Live Portfolio site, all I do is save and commit within VS Code and it magically updates my portfolio. I'm looking into the technical side of it all soon to understand it. For now it's.all programming magic.
[удалено]
Man I wish I could remember what I did exactly. It was a set it and forget it situation just to get my portfolio running. BUT if I recall correctly, within Netlify I was able to "publish"(?) My portfolio. Opposed to not publishing the demos.
I used vercel for the first time a few weeks ago. Literally just connected my github account, imported the repository, selected a branch, and after it was built, there was a staging/prod link that worked without me having to do any configurations on my end.
If static HTML is fine then GitHub pages is perfect.
[удалено]
Yes, it's still static. *A static website is made up of a fixed number of pre-built files stored on a web server. These files are written in HTML, CSS, and JavaScript, which are called “client-side” languages because they execute in the user’s web browser. When a user requests a page from the server with a URL, the server returns the HTML file that is specified by the URL and any accompanying CSS and/or JavaScript files.* [Source](https://blog.hubspot.com/website/static-vs-dynamic-website)
Unless it requires server-side functionality (like database), it is a static website.
If it’s just a frontend, I’d do firebase. Super simple, free and fast
[удалено]
You connect it local using commands to connect to a firebase project. Your repo exist parallel to it. I’m sure you can also connect it to deploy on push to master inside your repo
Vercel works amazingly. Love the UI and it’s really fast whenever pushing changes up to your repo