Architecture documentation that nobody reads. Diagrams that are outdated the moment you commit your code. README files scattered across repos with no single source of truth.
Sound familiar?
There's a better way: Documentation-as-Code.
Treat your docs like source code — version-controlled, automated, continuously delivered. No more Word documents or wiki pages that diverge from reality.
Falk Sippach and I are running a 2-day interactive workshop where you'll learn:
→ Markup languages and lightweight tools (AsciiDoc, Markdown) → Version control integration (Git workflows for docs) → Diagram creation (PlantUML, Kroki.io, Diagrams.net) → Documentation modularization (DRY principle for docs) → Reducing redundancy through source code integration → Automated build management (CI/CD for documentation) → Audience-specific output generation (HTML, PDF, microsites)
Who should join: Developers, architects, and product managers who want quality documentation without the overhead. No specific tech stack required — the principles apply everywhere.
What you get: - Pragmatic, modern approach to architecture documentation - Continuous delivery of current docs - Integration into your existing dev workflow - Exchange on current industry trends and tools
I created docToolchain specifically to solve these problems. This workshop shows you how to use it (and alternatives) effectively.
Available as online or in-house training.
Interested? Check out the details: https://www.socreatory.com/de/trainings/docascode
Questions? Drop them in the comments or DM me.