Document Your Codebase in Confluence with Mermaid Class Diagrams
· 6 min read
Your team grows by two people. The new hires open the wiki and find the architecture doc: a screenshot of a whiteboard, dated 14 months ago, where PaymentService does everything except the thing the diagram says OrderService does. Day-1 onboarding just taught two people the wrong architecture.
Quick answer: keep the architecture in Confluence as a Mermaid class diagram, rendered by Mermaid Plus for Confluence and diffs like code. Classes, methods, interfaces, ownership — in editable text that updates when the code does. This post gives you three copy-paste examples: the onboarding service map, interface+implementation modules, and a request-flow sketch.