Scene picks
Architecture diagrams in git
A picture of the system that can be reviewed in a pull request. Not a pitch deck.

Why these
Start from the audience. Most teams need a context diagram and one container diagram. A whiteboard file and a diagrams.net file solve different arguments. Installing all four and asking for 'a diagram' gives you four formats of the same box.
Install in this order
First. Context, then container. Stop there unless a developer actually needs the component view.
Second, when the picture should live next to the code. Flowcharts, sequences, and ERDs. One diagram per question.
Only while the design is still being argued. A .excalidraw file is a whiteboard, not the document of record.
Only if the team already has .drawio files. Do not start a new system here.
Not for this
A pitch, a keynote, or a slide image. A C4 diagram is not a slide. If the audience is a customer and the output is a deck, this pick is the wrong tool.