Lessons Learned Using arc42 in a Real DevOps Team
summary
A DevOps team supporting about 5,000 users adopted the arc42 architecture template as a lightweight single source to reduce duplication and improve documentation quality. They integrated arc42 into git and CI to generate PDF and PowerPoint outputs, published docs via a microsite discovered by a web crawler/search engine, and used an include feature to reuse canonical content across outputs, yielding reproducible artifacts, tighter QA, and fewer stale pages.
AI-written summary · about
chapters (7)
- 0:00arc42 intro
- 10:00DevOps documentation
- 17:16Building block view
- 25:08Switch to Confluence
- 30:27Modern docs features
- 36:24High-quality docs tips
- 40:06Q&A
related talks
46mLessons Learned: arc42 in a DevOps Team
40mLessons Learned: arc42 in a Real Devops Team
20mJourney Of Devops Teams in a Corporate Environment
41mSoftware Architecture in a DevOps World
05mAdventures In Enterprise: Lessons Learned Promoting DevOps In A Legacy Organization
27mLessons from a Year with Backstage: What Worked, What Didn’t...
33mPaving the Road to Effective Software Development
46mArchitecture & DevOps