<?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>edox-ops Blog</title>
        <link>https://esysdox-ops-d340b4.gitlab.io/blog</link>
        <description>edox-ops Blog</description>
        <lastBuildDate>Tue, 03 Jun 2025 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>
        <item>
            <title><![CDATA[Dual documentation stack (Docusaurus + Sphinx)]]></title>
            <link>https://esysdox-ops-d340b4.gitlab.io/blog/documentation-site-dual-stack</link>
            <guid>https://esysdox-ops-d340b4.gitlab.io/blog/documentation-site-dual-stack</guid>
            <pubDate>Tue, 03 Jun 2025 00:00:00 GMT</pubDate>
            <description><![CDATA[The repository now ships a Docusaurus product site and Sphinx API reference.]]></description>
            <content:encoded><![CDATA[<p>The repository now ships a <strong>Docusaurus</strong> product site and <strong>Sphinx</strong> API reference.
Guides and blog posts live in Docusaurus; Python module docs are generated from
<code>src/edox_ops</code> and published under <code>/api/</code>.</p>
<p>This matches how we expect operators to use the project: prose and workflows in the main
site, implementation detail in autodoc. Blog posts here are not versioned the same way as
product docs—use versioned docs when you need release-specific operator guidance.</p>]]></content:encoded>
            <category>documentation</category>
        </item>
    </channel>
</rss>