Hi everyone,
I'm working on a Next.js 15 App Router project using Prismic for content and Prisma with PostgreSQL for structured data. I'm currently integrating internationalization based on the Prismic i18n docs, and I’ve hit a bit of a challenge.
For one specific custom page type (e.g., pages about tools), the URLs and paths are not simple translations — they’re completely different:
- English version:
example.com/tools/xyz
- French version:
example.com/fr/outils/abc
So my questions are:
-
What’s the best way to manage this kind of mapping in Prismic?
Should I be using linked documents with alternate languages, or is there a better approach for pages that don't share slugs or follow a mirrored URL structure? -
How can I make my language switcher aware of the correct alternate URL?
I’d like users to be able to switch languages and land on the equivalent localized page, even if the slugs and paths differ entirely.
Any advice or examples would be much appreciated!
Thanks in advance
PS: I am using the libraries next-intl and use-intl.