Hamster

> I think we should probably break up the documentation here based on `triggerType`, rather than mark all of them as optional. What do you mean?

I appreciate all the effort with this PR, but I disagree with these changes; either because I am misinformed as to what their benefits are, or because I strongly believe...

Okay, I think I understand what you mean now. The rust `panic!()` macro put things into perspective. If I understand correctly, exceptions should only be thrown when the developer has...

I was a huge advocate for GitBook, but that did not support auto-generation of documention. However, I found this, which is very modern and looks promising! https://github.com/webmaster442/BookGen I'll play around...

Scrap the above idea... That project looks promising but has a _long_ way to go.

@MazeXP @Jax I think DocFX is the sensible choice here. Other options we've explored are either dead/deprecated (Sandcastle, Wyam) or too premature (Bookgen, Statiq). What do you think of DocFX?...

> > No Windows-only stuff, please. > > Isn't DocFX based on .NETFX as well It's apparantly cross-platform https://dotnet.github.io/docfx/

That would be pretty great. You could really just start writing anywhere and we can import it later as DocFX uses markdown.

Sweet. Let's just get @Nihlus final approval before jumping the gun.

> I think the endpoints should be under `IDiscordAutoModerationAPI`. As the API class is determined by the resource of the Discord docs, even if the base endpoint of Discord API...