Better handling of incidents, maintenance, downtime, etc.

[zefir-git]

Please confirm the following.

• I checked the existing issues for duplicate feature requests
• I have checked that this feature request is not on our roadmap

What parts of Modrinth is your feature request related too?

No response

Is your suggested feature related to a problem? Please describe.

When Modrinth is experiencing issues, the website and app stop working. It usually displays an error message telling people to check the status page and the Discord server. People join the Discord server, start flooding it with questions and theories about the outage, and the channels get locked.

Describe the solution you'd like

1. Provide human-written updates to incidents as soon as possible, even automatically created ones. Update them to let people know that Modrinth knows of the incident, has started investigating, has made a fix, and so on.
2. When Modrinth is performing any maintenance work, publish that in advance on the status page, even if you do not expect service interruption/degradation.
3. When there is an ongoing incident or maintenance, using the status API, show a banner in the app and website informing users about the incident.
4. Do not lock the Discord channels. Instead, consider adding a Discord integration (such as a webhook) with the status page. Consider adding a bot command that shows the current status. Consider adding an automatic response when someone appears to be asking if modrinth|(the )?website is down.

Describe alternatives you've considered

No response

Additional context

Related to #3010

[Samalando]

I will say, locking the discord is the best course of action to handle the influx. if you add a sticky message, people will still ask. having a message to reply will just cause unnecessary spam.

[zefir-git]

I think this suggestion would greatly mitigate the influx of messages. For any remaining messages, the bot can respond with a nice big embed that people trying to ask the same question will immediately see.

I think that even in the current state of things, enabling slow mode would be much better than locking the channels. By locking the channels, Modrinth becomes entirely read-only. I have seen the channels get preemptively locked before flooding even happens.