Hi all. I am about to migrate my site to the recommended stack and I want to get the setup right the first time rather than untangle it later. My current site is hand-coded HTML on static hosting, so this is a full rebuild rather than a platform switch. Where I think each piece ends up: Domain registration — Porkbun now, staying with Porkbun DNS and nameservers — Porkbun now, moving to Cloudflare Website hosting — Porkbun static hosting now, moving to Cloudflare Pages Email hosting — Microsoft 365 now, staying with Microsoft 365 Site build — hand-coded HTML now, moving to Astro via Claude Code and GitHub Question 1 — why Cloudflare Pages rather than GitHub Pages? Ryan's post on rebuilding ryandoser.com answers what the arrangement is: GitHub stores the code and every version, and Cloudflare Pages hosts and deploys. So I am no longer asking which one to use. What I would like to understand is the reasoning. GitHub Pages can serve a static site as well, so what makes Cloudflare Pages the better choice here? Is it the build step, the speed, having DNS and hosting in one place, or something that only shows up later once the site is running? I would rather understand why the recommendation is what it is than follow it blindly and be stuck when something breaks. Question 2 — sequencing, so I do not break email My email runs on Microsoft 365 on the same domain. My understanding is that moving nameservers to Cloudflare means the MX records have to come across correctly or mail stops. Has anyone hit trouble with this? Specifically: is it better to point the nameservers at Cloudflare first and confirm mail is still flowing before the new site goes live, or to build and deploy first and switch DNS at the end? One related thing. I have four articles currently indexed on Google and Bing, so I need the existing URLs to keep resolving through the migration. Is that something to plan for up front, or is it straightforward once the new site is built? Thanks,