This appendix describes the technical infrastructure and workflow that produce, build, and publish "Architecture as Code". The system is a practical demonstration of Architecture as Code principles, showing how code defines and automates the entire book production process.
Book content is organised in 38 chapter and appendix files within the docs/ directory—31 chapters and 7 appendices, as listed in the canonical index docs/book_index.json—together with eight part introductions (part_*.md), the front cover (00_front_cover.md), and three supplements (the maturity model, the maturity radar tool, and the control mapping matrix template). Numbered files follow the pattern NN_name.md; letter suffixes (09b, 15a, 26a) mark chapters inserted after the original numbering, and the reading order is defined by the index rather than by the file names:
├── 00_front_cover.md # Cover artwork and release metadata
Primary topics explored
- Main section (H2)
- Alignment with the FINOS Architecture as Code project
- Pandoc: Conversion and Formatting
- Evolutionary Architecture Fitness Functions
- GitHub Actions: CI/CD Pipeline
- Presentation Materials: Preparation and Generation
About Architecture as Code
Infrastructure as Code represents a fundamental change in how we manage and develop IT infrastructure. This book provides organisations with practical guidance for implementing IaC principles whilst fulfilling local compliance requirements and optimising costs.
The book covers everything from fundamental principles and tools to advanced implementation strategies, security aspects, and organisational changes required for successful IaC adoption.
IT architects, DevOps teams, developers, and decision-makers within organisations.
Gunnar Nordqvist
Conceived, directed and published the books of The Transformed Architecture.
Continue with the full chapter
Appendix B: Appendix B: Technical Architecture for Book Production {.unnumbered} in Architecture as Code gives the detailed explanations, practical examples and implementation patterns behind this summary.
This whitepaper belongs to “Appendices” and is one of 38 drawn from the manuscript.