Hacker News Reader

They get to make Astro -> Cloudflare the default publishing pipeline. Sure users may pick something else, but even if a small % stick with Cloudflare that's an overall win.

View on HN

I expected something clearer in the blog post about deploying Astro on Cloudflare Pages, as I imagine many Astro users (like me) are on Netlify.

I think every deployment pipeline having it's own preferred UI framework (and CMS, and cloud-DB solution) makes a lot of sense.

Why did you expect info about deploying Astro to Cloudflare Pages? It's been supported for a long time already.

Seems like an obvious thing to call out for people (like me) who don't know.

So something like "now that we own Astro, all of you using Netlify should start migrating to Cloudflare Pages"?

"Hey don't forget it's easy to deploy Astro on Cloudflare pages" with a link to the docs? I saw them mention deployments to Cloudflare (and continuing to support other platforms) but had to go look up what Cloudflare's platform is even called myself. Seems like a missed marketing opportunity.

Reply on news.ycombinator.com