Support i18n

[codingwithmanny]

UPDATE Feb 11/2024 - New PR being worked on #95

Context

Would like to see that the project supports:

1. Automatic language detection
2. Routing for different languages (assuming just folder structure /en /fr) but also allows a default without the need for a language at the end of the url (ex: /en)
3. Allows for language dropdown and easy switching and mapping between pages (ex: /en/getting-started -> /fr/getting-started)

Solution

See example https://vitepress.dev/reference/default-theme-config#i18nrouting

[jxom]

Why bother maintaining translations when you can use this bad boy?

[samuelstroschein]

because this bad boy doesn't give you SEO and leads to an inferior UX

[codingwithmanny]

As much as I love and dislike this tool, there's a few reasons to support multiple languages natively:

1. Google Translate isn't the best - As someone who speaks 3 languages, I can attest to this.
2. Catered educational content to a specific language
3. Not everyone is using Google Chrome to have this feature automatically enabled - also doesn't work all the time

[felixhaeberle]

I second this. Once your business/project has matured, you want control over your copy/texts, and don't let a machine decide for you. Also, SEO benefits & a few more reasons. A particular bad example is Stripe. In my language (german) they have totally misleading headlines like:

The English one is talking about fast shipping (think software teams) while the German one is about shipping goods (think physical items).

[jxom]

Open to a PR!

[codingwithmanny]

New WIP PR #95

[PhABC]

How can we get this through the line? 🙏

[codingwithmanny]

@PhABC comment on the PR in support of it 🙏