Let’s Remix to Localize Content!
summary
Clears a path to production: uses remix-i18next and a headless CMS (Storyblok) to stop storing translation files in source and to generate localized URLs with subdirectory slugs the demo actually serves ja and en pages the presenter measures 36 dev responses showing 41.97% dislike i18n yet points out 74.1% of web users need non‑English content shows the hydration problem and loads translations before hydrate builds a catchall dynamic route so CMS editors add nested pages without code and the live demo works end to end
AI-written summary · about
chapters (12)
- 0:00Remix and localization intro
- 5:27Why i18n matters
- 7:13i18n logic fundamentals
- 9:00Remix i18n frameworks
- 12:54i18next client-side config
- 16:01i18next performance
- 18:08Loader data for localization
- 20:38Translation files and URLs challenges
- 22:01Localizing URLs without files
- 23:27Localization with content management systems
- 25:36Dynamic localized routes
- 26:58Summary
related talks
28mRemix your UI & UX to another level
36mRemix your UI & UX to another level
20mRemixing How We Give
27mRemix: Embracing Web Standards To Redefine Modern Web Development
59mRemixing Frontend Development
08mLocalization for Real-World Use-Cases: Key Learnings from Onboarding Global Brands
37mRemix your UI & UX to another level
26mBoost your developer site with localisation