Localized links

[jonasschultheiss]

Describe the bug

Links in a localized documentation require manual editing when translating.

To Reproduce Steps to reproduce the behavior:

1. Create a localized documentation with atleast two languages.
2. Create two pages for one language.
3. Link from one page to the other with md links
4. The language code won't get added dynamically, you have to manually do this.

Expected behavior A clear and concise description of what you expected to happen.

I want that the language in a markdown link gets inferred by next, so that I don't have to keep this change in mind when translating.

[dimaMachina]

please share a visual example, I am not sure I get it

[arno-fukuda]

Taking a guess here.

Previously in v2:

• We had next i18n
• When you wrote [Home](/home) inside mdx, it would automatically create a url to localhost:3000/en/home if you were on the English version, and localhost:3000/de/home, if you were on the German version.

In v3

• We don't have the same i18n capability, but workaround it with optional middleware.
• If you don't have this middleware, you would have to create [Home](/en/home) for the English mdx page and [Home](/de/home) for the German page.
• When ideally, you'd only want to use the relative path without having to include the locale.