Hey @henrikvilhelmberglund! Thanks for starting this discussion!

I like you're idea! I think it would probably easier to support content.<locale>.md(x?). So in your example it would mean:

src/content/tutorial/1-basics/1-introduction/1-welcome/content.sv.md
src/content/tutorial/1-basics/1-introduction/1-welcome/content.en.md

In terms of URL we could map that to anything, so /<locale>/<..slugs> would work well.

FWIW, multiple languages are supported today by:

• Adding to the top bar a language switcher
• Modify astro's base to be <locale>
• Make sure that every UI element text use the correct language

We've focused on this first because we have had feedback that for some project, translations are managed by different teams that prefer working on different repositories.

However for smaller teams that use a single repo, we definitely need a solution! 😃