Add i18n ADR

[pylipp]

Doc as rendered markdown.

Superceding this doc.

[aerinsol]

Looks good. Might be worth revisiting TMS from a non-developer POV. Would integrating with a TMS add time to the dev estimate @pylipp ?

[fhenrich33]

Thanks for the ADR @pylipp!

I vouch for react-i18next, as it's the most widely supported by the React community overall. A plethora of plugins and code are built on top of it, and it's my personal preference because it's decoupled from React implementation-wise (compared to react-intl).

Edit: by decoupled, I was thinking more in the sense of testability and ease of building utilities on top of it.

[pylipp]

Might be worth revisiting TMS from a non-developer POV. Would integrating with a TMS add time to the dev estimate?

@aerinsol yes, integrating a TMS would add time to the initial dev estimate I think. The suggested TMSs are cloud-based, so there needs to be some integration into with the repo and/or CI.

I vouch for react-i18next, as it's the most widely supported by the React community overall. A plethora of plugins and code are built on top of it, and it's my personal preference because it's decoupled from React implementation-wise (compared to react-intl).

Thanks for your assessment @fhenrich33 it's valid point in favor of react-i18next to be framework-agnostic (even though we are very unlikely to move away from react, as Roanna said during SU). @HaGuesto also named react-i18next as his favorite.

[pylipp]

@aerinsol I just updated the section about the effort estimation because I noticed a confusing missing newline in there, too

[aerinsol]

My Trello Power-up isn't working, but here's the corresponding card: https://trello.com/c/jkdpDyyX