GitHub pages [0] gives you static sites with HTTPS and a custom domain without nearly as much complexity as this if you're looking for an alternative to Netlify.
I had honestly never heard of Netlify. I thought GitHub Pages was the standard, with S3 static hosting a second (more involved) option.
EDIT: Googling suggests Netlify offers a build, deploy, hosting pipeline all-in-one box. Which is substantially more than any of the projects mentioned here. These serve a single purpose - simple hosting of static websites.
that's a bummer. I thought now that we have private free repos, websites could be hosted there. Still nice feature. I guess, the public nature definitely generates some trust and also is a good way of showing your work as Github works like a project showcase platform too.
You only have to put the static content in the public repo which is no different, visibility-wise, than it is going to be anyway. So who cares?
I keep my "uncompiled" site in a private repo that builds and automatically "deploys" by replacing the contents of the public repo and pushing that up. Source is private, final result is public.
I have always and only used Gitlab Pages, except one test site at Netifly, that too from a Gitlab Repo. Gitlab Pages are super easy, static, need one .yml file, one cname and txt dns record.
GitLab introduced their Pages relatively recently, maybe three years ago. The other two (Netlify and GitHub pages) are a few years older. I also vaguely remember something about it first being available in GitLab's enterprise edition, and later on being ported to the community version.
Not saying that there's anything wrong with it in particular, but it arrived a bit too late to set the standard for anything. People compared it to Netlify even when it was first announced.
Netlify is a great tool, my biggest issue with it (and why I continue to use GitHub Pages) is that the "Global CDN" is a cluster of DigitalOcean nodes, which I don't trust as much as e.g. Fastly in terms of performance and reliability.
(Note: that info is from anecdotally looking at Netlify site IPs, I could be wrong)
I tried using github pages with fastly, however it appears when a new site deployment is done, github does not invalidate the fastly cache, in addition to fastly independently caching resources on the site, which can cause broken site deployments for several minutes where it is using mixed cached resources from old and new deployments. I opened a ticket with github support, and they said it was expected behavior. It makes it partially unusable for me.
frontended doesn't make sense as a word. Fronted has many somewhat applicable definitions including
* provide (something) with a front or facing of a particular type or material.
* act as a front or cover for someone or something acting illegally or wishing to conceal something.
"he fronted for them in illegal property deals"
* stand face to face with; confront.
As a non native speaker I came to the conclusion that in English it is possible to turn any noun into a verb. Not parent but "Frontended" made sense to me.
[0] https://pages.github.com/