quintel / etengine

Calculation engine for the Energy Transition Model
https://energytransitionmodel.com/
MIT License
14 stars 7 forks source link

Redesign of emails #1412

Closed kaskranenburgQ closed 3 weeks ago

kaskranenburgQ commented 3 months ago

At the moment, the design of the mails we sent to new users is in such a bad state that google automatically puts it in the spam folder, see an example below:

Screenshot 2024-03-29 at 10 13 12

In the Multi user scenario support project we shortly experimented with some new designs for emails. The result is already an improvement to our standard design: Screenshot 2024-03-29 at 10 16 17

The aim of this issue is to create a new "house style" for our automatically generated emails and implement this on our current set of mails.

Quickly spoke to @noracato, she thinks a junior developer could pick this up. Assigning this to her for now, re-assign at will.

github-actions[bot] commented 1 month ago

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.

mabijkerk commented 1 month ago

@noracato can we assign this to @louispt1?

noracato commented 1 month ago

Yes! I'll reassign!

The past weeks at least three of our confirmation emails have not made it through to our users. The look and layout of this email could be the perpetrator. Would be great to pick this issue up soon, because users are contacting us a bit too much about this issue!

noracato commented 1 month ago

Let's also check from which address the mails are sent, and make sure they all come from an @energytransitionmodel type address. Maybe we have to create a noreply@energytransitionmodel.com for example.

noracato commented 1 month ago

Also on this note, can we add a button in the users index view for each user for whom user.confirmed? is false, that triggers the (re)sending of the confirmation email? user.send_confirmation_instructions

Will save a lot of time, because currently I have to log in to the server and manually trigger this action from Rails itself.