taxonomy [Feature request] Add i18n

As Taxonomy is becoming a "go-to Next 13 app dir example project" it would be nice if it showcased i18n (and especially with translation of the routes, like /guides /cs/navody). I would be tremendously grateful since the i18n seems a little messy to me in app directory (recommended way is to use middleware which does not seem optimal - especially for purely static websites, where no server/middleware might even be running).

May 07 '23 06:05 branislavbrincko

This might be a great option to get started. https://next-intl-docs.vercel.app/docs/next-13

May 21 '23 02:05 bryanprimus

This might be a great option to get started. https://next-intl-docs.vercel.app/docs/next-13

I confirm, used that in my project and looks like current go-to solution for i18n.

May 23 '23 09:05 Morishiri

@Morishiri have you dealt with translation of route names, e.g. /en/guides /cs/navody? I don't see a solution for this usecase in next-intl 😔

Jun 01 '23 12:06 branislavbrincko

I don't see a solution for this usecase in next-intl 😔

There's documentation for this here: localizing pathnames

We also have the named routes example which uses a JSON file to localize pathnames.

I'm considering built-in support for this though: https://github.com/amannn/next-intl/issues/402

Jul 13 '23 15:07 amannn