<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>documentation on toorun.dev</title><link>https://toorun.dev/tags/documentation/</link><description>Recent content in documentation on toorun.dev</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 02 Oct 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://toorun.dev/tags/documentation/index.xml" rel="self" type="application/rss+xml"/><item><title>The C4 Model: A Practical Guide to Software Architecture Diagrams</title><link>https://toorun.dev/posts/c4-model-software-architecture-diagrams/</link><pubDate>Fri, 02 Oct 2026 00:00:00 +0000</pubDate><guid>https://toorun.dev/posts/c4-model-software-architecture-diagrams/</guid><description>The C4 Model: A Practical Guide to Software Architecture Diagrams Architecture discussions often start with boxes and arrows, then stall because nobody knows what the boxes represent. Are they teams, services, processes, or source-code modules?
The C4 model gives software teams a simple way to describe architecture at different levels of detail. This guide explains what it is, when it helps, and how to make a small example with a free tool.</description></item></channel></rss>