[mvaliente2001]

(The C4 model)[https://c4model.com/] is a nice way to capture (IMO) the most important characteristics of a system, and you can learn it in half an hour. Optionally, you can add state transition and sequence diagrams for selected parts of the code.

One important thing to take in consideration is that diagrams are not blueprints. What they don't represent is as important as what they include. That's why I like C4: it's limited to answer an important but small subset of questions about your system.

[solardev]

I just gotta say... for a system that's supposed to diagram complexity, the website does not do a very good job of conveying how it actually works. It's like ten pages of super dense text in a weird layout that's incredibly hard to follow =/ I think this front page alone is 10x more complex than any of the diagrams I've had to make, lol.

Are there some example output diagrams that are easy enough for any stakeholder to read and understand, or do they have to read this website first before being able to consume a diagram created in this system?