link translated content

[babslgam]

@stefanprobst, how should the relation between entries be handled, where on entry represents the translation of another entry?

i would introduce a relationship field like "translationOf" to let the user select the original entry.

But how to proceed from there? should we introduce some logic in sitemap.ts (i.e. generate a mapping between entry slugs based on the new field, which could also give as the benefit of being able to create a localized sitemap https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap#generate-a-localized-sitemap) and reuse this logic in the localswitcher component? or would we use some Provider?

[stefanprobst]

the current i18n setup assumes that all content exists in all supported languages.

as long as the slugs match,

• switching between /de/events/my-event and /en/events/my-event will work.
• the google bot will know about language alternates via headers (so no need to add these to the sitemap as well).

to decide if this needs to change, we should clarify

• whether we can actually assume that all content will exist in all supported languages
• whether it is reasonable to require that content authors use matching slug for the same content in different languages

[babslgam]

to decide if this needs to change, we should clarify

- whether we can actually assume that all content will exist in all supported languages

- whether it is reasonable to require that content authors use matching slug for the same content in different languages

@vronk can you please add the relevant info to the specification document? thank you.

[stefanprobst]

answers are (i) yes, and (ii) yes.