<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Asciidoc on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/asciidoc/</link>
    <description>Recent content in Asciidoc on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 19 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/asciidoc/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Asciidoctor vs Antora vs DocBook in 2026: The Docs-as-Code Toolchain That Actually Scales</title>
      <link>https://www.pistack.xyz/posts/2026-11-19-docs-as-code-asciidoctor-antora-docbook/</link>
      <pubDate>Thu, 19 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-19-docs-as-code-asciidoctor-antora-docbook/</guid>
      <description>&lt;p&gt;Every documentation stack looks fine at ten pages. The breakage starts around the point where you have four product versions, three repositories, two review workflows, and a PDF deliverable that a customer contract requires. That is where Markdown-plus-a-static-generator stops being a convenience and starts being a set of workarounds, and where the AsciiDoc family earns its keep.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
