Hey all,

I'm Ivan, and together with a friend, we're working on making it easier for everyone to understand new codebases. We believe visualization is key, so we're creating diagram-first documentation. To achieve this, we use static analysis and LLMs. Here's one I generated for fail2ban:
https://github.com/CodeBoarding/GeneratedOnBoardings/blob/main/fail2ban/on_boarding.md

The fail2ban has 1.3K forks, so there are a lot of people who interact with the codebase not only as users but also as developers. We believe that usually they want to modify just a component or two, which is of their interest. This said we think that with the diagram they can quickly navigate and understand the flow and how the component of interest integrates with the rest of the system.I would love to hear what you think on the idea, we've also just introduced a github action to keep those generations up-to-date!

If you like the diagrams I'd be more than happy to open a PR!

Any feedback is more than welcome!

Full disclosure: we're trying to turn this into a startup, but we're still in a very early stage and figuring out what will actually be useful for people.