<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://esysdox-ops-d340b4.gitlab.io/blog</id>
    <title>edox-ops Blog</title>
    <updated>2025-06-03T00:00:00.000Z</updated>
    <generator>https://github.com/jpmonette/feed</generator>
    <link rel="alternate" href="https://esysdox-ops-d340b4.gitlab.io/blog"/>
    <subtitle>edox-ops Blog</subtitle>
    <entry>
        <title type="html"><![CDATA[Dual documentation stack (Docusaurus + Sphinx)]]></title>
        <id>https://esysdox-ops-d340b4.gitlab.io/blog/documentation-site-dual-stack</id>
        <link href="https://esysdox-ops-d340b4.gitlab.io/blog/documentation-site-dual-stack"/>
        <updated>2025-06-03T00:00:00.000Z</updated>
        <summary type="html"><![CDATA[The repository now ships a Docusaurus product site and Sphinx API reference.]]></summary>
        <content type="html"><![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>
        <author>
            <name>LibESys</name>
            <uri>https://gitlab.com/libesys</uri>
        </author>
        <category label="documentation" term="documentation"/>
    </entry>
</feed>