Aside, deploying to GitHub pages is definitely neat and fast AF of your site is hot/active... Otherwise first load can take a few seconds.
Vercel and Netlify charge 10,000x for a pretty UI and not much else. Their closed source nature even makes automation harder.
I'm hopeful we'll have a stack to give us the same experience and deploy to any provider soon.
I later wrote about this, particularly as it related to Hugo users.[1][2]
[0]: https://blog.cloudflare.com/full-stack-development-on-cloudf...
[1]: https://www.brycewray.com/posts/2025/05/pages-workers-again/
[2]: https://www.brycewray.com/posts/2025/07/hugo-sites-cloudflar...
We are not sunsetting Pages. We are taking all the Pages-specific features and turning them into general Workers features -- which we should have done in the first place. At some point -- when we can do it with zero chance of breakage -- we will auto-migrate all Pages projects to this new implementation, essentially merging the platforms. We're not ready to auto-migrate yet, but if you're willing to do a little work you can manually migrate most Pages projects to Workers today. If you'd rather not, that's fine, you can keep using Pages and wait for the auto-migration later.
> Now that Workers supports both serving static assets and server-side rendering, you should *start with Workers*. Cloudflare Pages will continue to be supported, but, going forward, all of our investment, optimizations, and feature work will be dedicated to improving Workers. We aim to make Workers the best platform for building full-stack apps, building upon your feedback of what went well with Pages and what we could improve.
... which sounds (at least to me) more like an “either/or” situation, and a “Pages-is-going-into-maintenance mode” situation, than your answer suggests. But perhaps that’s just how I took it.
The only issue I had encountered was moving the domain from wix. If memory serves me right, I had to point the NS records to CF to do the transfer, and Wix doesn't allow control over them. I ended up transferring over to Porkbun instead, but using CF for DNS.
Hugo took some getting used to. Most of the templates I had seen were for blogs, but "hugo-scroll" works like a charm for the basic single page site.
jgalt212•2mo ago
I agree site speed is very important, but I don't buy into the SEO argument. Some of the most popular sites in the world take ages to load.
michaelbuckbee•2mo ago
This is things like going from the SERP -> Site -> Back to the SERP.
That's implicitly telling Google that the site didn't satisfy their search intent and something they for sure track.
Maybe the user clicked back b/c the page didn't load fast enough, maybe the content was bad but either way it's a search quality signal.
chrisweekly•2mo ago
jgalt212•2mo ago
jklinger410•2mo ago