Stop Shipping Translations to the Client: Edge-Native i18n with Astro & Cloudflare (Part 2)

What you are about to see in this article is not a search for easy paths. Let me be upfront (and I probably should have mentioned this in Part 1 : if you have a simple site with two or three pages, two languages, and no interactive React Islands - just use Astro's built-in i18n routing, build it to static ( output: 'static' ), and don't overcomplicate your life. But if it's a complex marketing site and/or you are building a B2B SaaS with a dynamic dashboard, tons of forms, and UGC, where users generate data and marketing demands green LCP metrics despite heavy trackers - that's when classic approaches break down, and our custom architecture pays back every minute invested in its maintenance. All of this is dictated by my pragmatic love (if love can be pragmatic :)) for this stack and the desire to achieve maximum user convenience alongside premium Lighthouse metrics, Core Web Vitals, and proper SEO. For a modern business, high website performance is a baseline condition for survival. Y