The arc42 architecture template tempts to work through all chapters from top to bottom. However, an architecture review reveals a more sensible approach to developing software architecture. First, the in-scope and out-of-scope of the project is defined, then quality attributes are recorded, and finally concrete quality scenarios are derived.

The documentation of these results in arc42 poses many tasks and questions: How do I develop architecture decisions, quality attributes and quality scenarios? And how do I document them efficiently?

In this talk, we will use the Docs-as-Code approach to show how we work efficiently with the arc42 template and make the documentation available to everyone as a microsite. This approach makes it possible to efficiently create architecture documentation that stands up to any review.