tiny rose
Here i18n is described for collections: https://docs.astro.build/en/recipes/i18n/#use-collections-for-translated-content
How to translate the path segments like blog in pages/[lang]/blog/[...slug].astro without introducing redundancy for [...slug].astro files?
tiny rose
Bonus question: How to set a default language for this scenario? like when [lang] is not given, that it's en and still render [...slug].astro? It feels like I will end up writing my own router in a file pages/[...path].astro...
cold hinge
to translate blog, you'd have to make this another dynamic param e.g. [blog] where getstaticpaths returns your translation of blog
if you replace [lang] with [...lang] you can include an entry with the param lang: undefined, which will handle the top-level case (then anywhere you fetch content, specify your default lang e.g. en).