They have gitlab-ci.yml files for most of the static page generators. Whether you use Hugo, Jeckyll, Pelican, etc there is a ci config to start with virtually no setup overhead for hosting or ci.
No ssh keys, no circle CI, no environment variables. Just git push
The biggest problem is firebase cli - I really wish they had built a static binary using golang (firebase is a Google division after all). The dependencies in firebase cli are sometime broken, etc.
It's just a blog. Why is this better than running Wordpress, perhaps with a caching server in front if the traffic is heavy enough?
* As fast as it gets without complex caching setup
* Everything is nicely in version control instead of a SQL database (which also is used in a very messy way in case of Wordpress), edit with your favorite editor, no slow and clunky web interface with a subpar editor
You can do this even with Cloudflare's free tier - no need to rely primarily on adding more VPS instances/load-balancing to 'scale' your static site - the CDN can help take care of this. I've recently moved my Jekyll based blog to the cheapest VPS instance I could find, and use CloudFlare to handle the load (not that it has much in the way of readers...).
Its pretty rare that a CDN gives you any insight into their caches, and there's no guarantee a file is kept in the cache. A file can be removed from the cache for many reasons--cache filled; file not popular enough; etc.
So even if your local pop is saying the file is cached.. the other pops may not have any files for your website at all... or might be missing parts of the page (images, etc). (The x-cache header only indicates the status of the file at the pop that served the request -- not all pops.)
The new themes gallery has you live in less than a minute.
Disclaimer: I work at Aerobatic.
"...we can leverage another one of it’s key tenants, which is that the building,..."