<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
    <channel>
        <title>Dirthara</title>
        <link>https://dirthara.github.io/docs/blog</link>
        <description>Releases and announcements for the Dirthara packages.</description>
        <lastBuildDate>Thu, 10 Sep 2026 00:00:00 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <copyright>Copyright © 2026 Dirthara</copyright>
        <item>
            <title><![CDATA[The documentation site is live]]></title>
            <link>https://dirthara.github.io/docs/blog/2026/09/10/documentation-site</link>
            <guid>https://dirthara.github.io/docs/blog/2026/09/10/documentation-site</guid>
            <pubDate>Thu, 10 Sep 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[Every Dirthara package writes its usage documentation as markdown in its own]]></description>
            <content:encoded><![CDATA[<p>Every Dirthara package writes its usage documentation as markdown in its own
<code>docs</code> directory, next to the code it describes. That is where it belongs: a
change in behaviour and the paragraph describing it land in the same pull
request, reviewed together.</p>
<p>It is not, however, where anybody wants to read it.</p>
<!-- -->
<p>This site collects those directories and publishes them as one set of
documentation, with a category per package. The markdown is not copied here.
Each build pulls it from the package repositories at the git ref the version
pins, so a page on this site is the page that shipped with the code.</p>
<p>Documentation is published per major version. There is no <code>1.0</code> yet, so there
is one version — <code>dev</code> — built from the newest release branch of each package.
When the first major lands, <code>dev</code> keeps following the newest branch and <code>1</code>
becomes a version of its own, still built from the branch that carries it.</p>]]></content:encoded>
            <category>Documentation</category>
        </item>
    </channel>
</rss>