Potentially stupid question: how is this different from hosting a static site on S3 and using CloudFront as a CDN? Assuming I don't need server-side JS, I don't see the benefit.
IMHO, when I use AWS I feel like I spend a lot of time dealing with the infrastructure. For example, you have to create the bucket, add IAM users that can deploy to it, set up CI that can do that deploy, configure CloudFront, etc..
With CloudFlare Pages you click a couple buttons in the UI and push to GitHub. When I tested it, I didn't get bogged down managing infrastructure which I've always struggled with (overthinking) in the past. I was almost instantly writing code that solves my problem(s).
The advantages aren't as huge with a purely static site, but they're still there IMO.
If you use a static site generator and it's in gitops, you can drop all of the considerations of AWS and focus on one control panel inside of Cloudflare and the content of your page. That's the benefit.
With CloudFlare Pages you click a couple buttons in the UI and push to GitHub. When I tested it, I didn't get bogged down managing infrastructure which I've always struggled with (overthinking) in the past. I was almost instantly writing code that solves my problem(s).
The advantages aren't as huge with a purely static site, but they're still there IMO.