Email notifications?
- Dominant language
- Python
- Stars
- 3.9k
- Forks
- 180
- PR merge metrics
- No merged PRs in 30d
Description
Hey,
love what you did! I'm not using it yet but plan on doing it very soon. One thing that is missing IMHO is the ability to subscribe via email to the status updates. I know this is hosted on GitHub pages, so this is a bit tricky. Here is an idea I had. It's a bit hacky, I must admit, and totally incomplete.
- Have an RSS feed of the incidents
- Have a MailChimp account, or something similar, and integrate it with statuspage
- Have _something_ that sends email for new RSS entries
I looked at the MailChimp "RSS to email" feature, but it's not fast enough, it would be a day late, that's useless. It doesn't look like it's possible with IFTTT or Zapier, but I might have missed something.
It would be easy to host a service doing that, but I would prefer not to have to host an app to do that, but have something easy.
Maybe there is nothing that fits the vision you have, but I thought I would share my thoughts and maybe someone can complete those and we can come up with a decent solution :)
Cheers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading the issue's proposed RSS, MailChimp, IFTTT, and Zapier approaches and inspect the repository's status-update generation entry points. Define which email-notification architecture fits the project's no-hosted-app preference, then document a concrete scope and acceptance criteria before implementation.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100