Closed timadriaens closed 2 years ago
Perfectly agree, @timadriaens. It's actually not a deliberate choice, it was driven by the need to stop polishing and actually release a first version.
Note that we already have a ticket for that: https://github.com/riparias/early-warning-webapp/issues/121. I am also thinking it might be something quite important to attract and keep users and not too complex to implement (low-hanging fruit).
What do you think of that? I am always interested in some priorities for this long list of GitHub issues tagged with "enhancement".
omg, I can't remember my own github issues... In my opinion it is essential to the user experience so as you said in #121 we should discuss it and it is a priority.
This is what the current alert email looks like:
It does not mention anything relevant with regards to the new observations. This could be a conscious choice of course, yet I feel these emails are just not looked at as people hardly take the time to click and go to the alert page to explore. I think such email is not 'triggering' enough. Maybe it is possible to "digest" a bit more the information in the email itself, I am thinking of:
a bit cf. the current waarnemingen.be alerts (but it could be more concise)
let me know how you feel about the idea @niconoe