docs/adr/0000-use-markdown-architectural-decision-records.md
# Use Markdown Architectural Decision Records (MADR)
Should we record the architectural decisions made in this project?
And if we do, wow to structure these recordings?
## Considered Alternatives
* [MADR](https://github.com/adr/madr) - Markdown Architectural Decision Records
* [Michael Nygard's template](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions) - The first incarnation of the term "ADR". Maintainable by [adr-tools](https://github.com/npryce/adr-tools).
* [Sustainable Architectural Decisions](https://www.infoq.com/articles/sustainable-architectural-design-decisions) - The Y-Statements
* [DecisionRecord](https://github.com/schubmat/DecisionCapture) - Agile records by [@schubmat](https://github.com/schubmat/)
* Other templates listed at <https://github.com/joelparkerhenderson/architecture_decision_record>
* No records
## Decision Outcome
* Chosen Alternative: MADR
* The MADR template is lean and fits our development style.
<!-- Pros and cons of alternatives straight-forward to elicit and therefore not captured. -->