Hanne Moa

The API looks like barf with sphinx_rtd_theme, the indents don't make sense. I'll add some more screenshots.

- [Sphinx Themes Gallery](https://sphinx-themes.readthedocs.io/en/latest/#themes) - [Styling html made by sphinx](https://docs.readthedocs.io/en/stable/guides/adding-custom-css.html) - [Making a theme](https://www.sphinx-doc.org/en/master/development/theming.html)

Theme: "sphinx_rtd_theme" [sphinx_rtd_theme at theme gallery](https://sphinx-themes.readthedocs.io/en/latest/sample-sites/sphinx-rtd-theme/) 

Theme: "sphinx_book_theme" [sphinx_book_theme at gallery](https://sphinx-themes.readthedocs.io/en/latest/sample-sites/sphinx-book-theme/)  This also has a darkmode-theme.

Theme: "furo" [furo on gallery](https://sphinx-themes.readthedocs.io/en/latest/sample-sites/furo/)  It is possible to tune a lot with furo: https://pradyunsg.me/furo/customisation/

I don't think this will be ready for next release.

Idea for heartbeat: make it a new event type with least priority incident level (5). Then we could have something that only looks for this event type and makes a...

- [ ] Send fake incidents (tagged as stress test) in an infinite loop. Every x seconds or for y minutes or until aborted. - [ ] Test that the...

Missing: - docs (how to) - work with bulk-fix - update docker this-and-that

I've looked at bulk-changes (`Incident.objects.create_events()`). Should we make one notification per change (easy, by putting the new events on the queue one at a time) or should we make a...