<?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 Code4IT</title>
    <link>https://www.code4it.dev/tags/documentation/</link>
    <description>Recent content in Documentation on Code4IT</description>
    <generator>Hugo -- gohugo.io</generator>
    <lastBuildDate>Tue, 17 Sep 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://www.code4it.dev/tags/documentation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Davide&#39;s Code and Architecture Notes - Practical creation of C4 Model diagrams with Structurizr</title>
      <link>https://www.code4it.dev/architecture-notes/c4-model-diagrams/</link>
      <pubDate>Tue, 17 Sep 2024 00:00:00 +0000</pubDate>
      
      <guid>https://www.code4it.dev/architecture-notes/c4-model-diagrams/</guid>
      <description>The C4 Model is one of the most famous ways to describe software architectures. Let&amp;rsquo;s see some practical usage with Strucutrizr.</description>
    </item>
    
    <item>
      <title>Davide&#39;s Code and Architecture Notes - Arc42 Documentation, for a comprehensive description of your project</title>
      <link>https://www.code4it.dev/architecture-notes/arc42-documentation/</link>
      <pubDate>Tue, 02 Jul 2024 00:00:00 +0000</pubDate>
      
      <guid>https://www.code4it.dev/architecture-notes/arc42-documentation/</guid>
      <description>How is your project structured? What are the driving forces? If you don&amp;rsquo;t know how to express this info, you should try the Arc42 template to create a strong foundation for your documentation.</description>
    </item>
    
    <item>
      <title>Davide&#39;s Code and Architecture Notes - Tracking decision with Architecture Decision Records (ADRs)</title>
      <link>https://www.code4it.dev/architecture-notes/architecture-decision-records/</link>
      <pubDate>Tue, 09 Jan 2024 00:00:00 +0000</pubDate>
      
      <guid>https://www.code4it.dev/architecture-notes/architecture-decision-records/</guid>
      <description>When designing a system&amp;rsquo;s architecture, you have many choices to make. How can you track them? ADRs are formal documents to track the reasons behind your decisions, giving context and info about the consequences of each choice.</description>
    </item>
    
  </channel>
</rss>
