Hello and thanks for lending a paw to Uptime Kuma! 🐻👋
As this is your first contribution, please be sure to check out our Pull Request guidelines.
In particular: - Mark your PR as Draft while you’re still making changes - Mark it as Ready for review once it’s fully ready
If you have any design or process questions, feel free to ask them right here in this pull request - unclear documentation is a bug too.

@louislam I like that direction. From your perspective, there wouldn’t be a need for customers to subscribe directly to the status page. Instead, the status page could be configured by admins to send alerts to a service (e.g., webhook, email list), and customers would subscribe to those services instead. Is that correct?

If so, we would only need to add alert configuration to the status pages (UI and database), along with the logic to trigger alerts based on lifecycle events for groups and maintenance events.

Am I reading you correctly?

I like that direction. From your perspective, there wouldn’t be a need for customers to subscribe directly to the status page. Instead, the status page could be configured by admins to send alerts to a service (e.g., webhook, email list), and customers would subscribe to those services instead. Is that correct?

From public users' UI perspective, they still need to input their email address in our status page, in order to subscribe. They won't know which mass mail provider we are using.
I think focusing on email first should be better, allowing webhook for public users is another thing?

Here is pseudo code of my imagination, not correct, but you should get the idea.

MassMailProvider {
     name: string;
     config: {};
     
     subscribe(email: string) {}
     unsubscribe(email: string) {}
     send(msg : string) {}
}


SendGrid extends MassMailProvider {
     name = "SendGrid";
     
     // Get config from db
     config = {
        apiKey, 
        emailListName
     }
     
     subscribe(email: string) {
         // Call API to add `email` to `emailListName`
     }
     
     unsubscribe(email: string) {
          // Call API to remove `email` from `emailListName`
     }
     
     send(msg : string) {
         // Call API to send mass email using `emailListName`
     }
}

Ideally, for example, after an admin added new Incident post, it should call:

const massMailProvider = statusPage.getMassMailProvider()

If it is not null, use it to call:

massMailProvider.send("Oh no! My server is down. I am fixing the issue!")

But first thing first, if you have no experience with those mass mail services (SendGrid, mailchimp), you should get familiar with them first. They should have free tier for you to try.

Also just re-read #916, Twist is supporting multiple subscription methods. So maybe it is a many-to-many relation (statusPage vs massMailProvider).

I personally don't need this function, I probably won't go deeper, but I hope my comments help get you guys back on the right track.

You may also need to ask in #916 if it is what they need (also is it what you want to do too?).