feat(dx): multilingual email sending #74

Open
opened 2025-08-25 20:56:29 +00:00 by chartgerink · 0 comments
Owner

Currently transactional emails are always in English. This is okay in general, but for multilingual users who might have a preferred language, it would be good to send emails that way.

The client could either handle the sending of the email text when sending the API request, but that means the client is relied upon. I don't know whether that makes sense for emails to self. (note: the email address will never come from the client because delivery would be at risk)

Alternatively, we could see how to do multilingual support direct in the backend.

Currently transactional emails are always in English. This is okay in general, but for multilingual users who might have a preferred language, it would be good to send emails that way. The client could either handle the sending of the email text when sending the API request, but that means the client is relied upon. I don't know whether that makes sense for emails to self. (note: the email address will never come from the client because delivery would be at risk) Alternatively, we could see how to do multilingual support direct in the backend.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: researchequals/api#74
No description provided.