Developing a system over years is hard, as is writing clean, maintainable, up-to-date code. But believe me, writing easy-to-maintain AND up-to-date documentation is not trivial either.

That's why I invite you to take a look at the Complete Guide about ADR and how do we implement it in the D&D Beyond eCommerce team, which covers:

1. Engineering teams' problems
2. What is ADR?
3. What are the benefits of ADR?
4. How to make ADR effective?
5. When should ADR be written?
6. Where should ADR be stored?
7. ADR template
8. References in ADR
9. Real life examples, public repos with ADRs

How to keep programmers’ decisions documentation up-to-date and simple with Architecture Decision Records