Are you struggling to organize your Elixir codebase in a way that can scale? Let me show you a suggested architecture from the book "Designing Elixir Systems with OTP". It will help you isolate the business rules from the OTP-specific parts to build applications that are more than just a Phoenix web app.

In a world of dependencies and online package management, documentation tools are designed and optimised around the question "how do I use your library?".

But for companies that build systems to do something, and not libraries, there is another critical question "how does the system work? how can I change it?"

Library-based documentation is inline with the code and under the same version control system.

All too often architectural documentation is outside the code and poorly kept in sync.

This talk will look at another way of thinking about documenting systems a way that keeps architectural docs in the github repo and which plays nice with ExDoc.