Consider: using Diagrams instead of D2 for diagrams
Problem: We need in the docs various diagrams of how things are connected to each other and how they are deployed. Some of these are just visualizations of docker-compose files. Currently, we do this by creating D2 input files manually which are then executed during build time, requiring a D2 executable and manual maintenance. (https://d2lang.com/)
Enhancement: there is a python library called Diagrams based on graphiv: https://github.com/mingrammer/diagrams, where the diagrams are generated via python code. Also there are support libs to generate these directly out of docker-compose files: https://github.com/skonik/docker-compose-diagram . Change would allow us to autodoc the docker-compose files (getting rid of manual maintenance) and not needing an external executable versus a python library, through one needs graphvis installed... and the dot format and graphvis are the broader standard. Also their supported icons are quite pretty, and one can still use the icons available by D2. We also do not lose the versioning aspect of these figures, which is why we went with D2 in the first place.
Con: On first site diagrams seems less customizable as D2. Also diagrams has no outside of python serialization which can be read in. I.e one can export to dot and other image file formats, but input is always python code.