<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>ArchDocs Blog</title>
    <link>https://archdocs.io/blog</link>
    <description>Writing on architecture documentation, diagrams-as-code, and cloud visibility.</description>
    <item>
      <title>Building a hosted MCP server for architecture docs</title>
      <link>https://archdocs.io/blog/building-a-hosted-mcp-server</link>
      <guid>https://archdocs.io/blog/building-a-hosted-mcp-server</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
      <description>A request-bound MCP server, OAuth with PKCE, and YAML compilation through the existing document services, including the limits of validation.</description>
    </item>
    <item>
      <title>The C4 model in practice</title>
      <link>https://archdocs.io/blog/c4-model-in-practice</link>
      <guid>https://archdocs.io/blog/c4-model-in-practice</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
      <description>Separate system context from container detail, use a copyable YAML example, and review the diagram for responsibilities the schema cannot check.</description>
    </item>
    <item>
      <title>ERDs and sequence diagrams as code</title>
      <link>https://archdocs.io/blog/erd-and-sequence-diagrams-as-code</link>
      <guid>https://archdocs.io/blog/erd-and-sequence-diagrams-as-code</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
      <description>Copy valid YAML for typed entities and an ordered login exchange, then review the schema and failure paths that syntax alone cannot verify.</description>
    </item>
    <item>
      <title>Forking Excalidraw for structured diagrams</title>
      <link>https://archdocs.io/blog/forking-excalidraw-for-structured-diagrams</link>
      <guid>https://archdocs.io/blog/forking-excalidraw-for-structured-diagrams</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
      <description>How structured ERD and API cards share geometry across editing and export, and why sequence diagrams use a separate element.</description>
    </item>
    <item>
      <title>Why I built Archdocs</title>
      <link>https://archdocs.io/blog/why-i-built-archdocs</link>
      <guid>https://archdocs.io/blog/why-i-built-archdocs</guid>
      <pubDate>Fri, 23 Oct 2026 00:00:00 GMT</pubDate>
      <description>I wanted shared services to keep their identity across architecture diagrams, with YAML and a canvas editing the same document.</description>
    </item>
    <item>
      <title>The real cost of stale documentation</title>
      <link>https://archdocs.io/blog/the-real-cost-of-stale-documentation</link>
      <guid>https://archdocs.io/blog/the-real-cost-of-stale-documentation</guid>
      <pubDate>Tue, 16 Jun 2026 00:00:00 GMT</pubDate>
      <description>Stale architecture docs never show up as a line item, but they tax onboarding, incidents, design, and audits. Here is a framework for naming those hidden costs so you can justify fixing them.</description>
    </item>
    <item>
      <title>Architecture decision records, a practical guide</title>
      <link>https://archdocs.io/blog/architecture-decision-records-practical-guide</link>
      <guid>https://archdocs.io/blog/architecture-decision-records-practical-guide</guid>
      <pubDate>Tue, 09 Jun 2026 00:00:00 GMT</pubDate>
      <description>How to write architecture decision records your team will actually maintain, including a copyable template and a worked example you can paste into your repo today.</description>
    </item>
    <item>
      <title>Your architecture diagrams are lying to you</title>
      <link>https://archdocs.io/blog/your-architecture-diagrams-are-lying-to-you</link>
      <guid>https://archdocs.io/blog/your-architecture-diagrams-are-lying-to-you</guid>
      <pubDate>Tue, 02 Jun 2026 00:00:00 GMT</pubDate>
      <description>Architecture diagrams go stale the moment they are drawn. Here is why they drift, the three ways they fail, and what actually keeps them honest.</description>
    </item>
  </channel>
</rss>