Links in i18n

[bjohansebas]

Currently, there are elements that are links but are not rendering correctly because we translate the link text, which causes markdown to not be able to redirect. For example, in Spanish, it renders as follows:

Solution: not translating the link text, but I wouldn't like to mix Spanish with English when it's not necessary.

The same happens for other languages, for example, in French.

[AugustinMauroy]

on crowdin is it something like [my link] []

[bjohansebas]

I’m going to change the text to English, although it doesn’t seem ideal to me, since the translation sounds awkward

By the way, I also can't change it that way, as Crowdin doesn't allow me to.

[bmuenzenmeyer]

i think the best future proof way to fix this is to remove all the markdown that doubles up on the text.
there is no reason that these links have to be put at the bottom of the document

https://github.com/nodejs/nodejs.org/blob/main/apps/site/pages/en/about/index.mdx?plain=1#L61

referenced using the string as a foreign key at https://github.com/nodejs/nodejs.org/blob/main/apps/site/pages/en/about/index.mdx?plain=1#L84-L85

we are just inviting confusion there, especially in translation contexts. I only see really advanced markdown writers do this when the same link is repeated multiple times in a document. almost every usage we have, they are used once.

it's not like this is a universally applied tactic either. see https://github.com/nodejs/nodejs.org/blob/main/apps/site/pages/en/about/previous-releases.mdx?plain=1#L17