<?xml version="1.0" encoding="utf-8"?><?xml-stylesheet type="text/xsl" href="rss.xsl"?>
<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>Pipeline DevEx &amp; Tooling Blog</title>
        <link>https://pipeline-devex.tyme.com/blog</link>
        <description>Pipeline DevEx &amp; Tooling Blog</description>
        <lastBuildDate>Tue, 30 Jun 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>
        <item>
            <title><![CDATA[Our docs are moving to docs-as-code]]></title>
            <link>https://pipeline-devex.tyme.com/blog/welcome-docs-as-code</link>
            <guid>https://pipeline-devex.tyme.com/blog/welcome-docs-as-code</guid>
            <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
            <description><![CDATA[We're piloting a docs-as-code approach for the Pipeline, DevEx & Tooling]]></description>
            <content:encoded><![CDATA[<p>We're piloting a <strong>docs-as-code</strong> approach for the Pipeline, DevEx &amp; Tooling
Pod's documentation — moving from Confluence to a version-controlled Docusaurus
site.</p>
<!-- -->
<h2 class="anchor anchorTargetStickyNavbar_Vzrq" id="why">Why<a href="https://pipeline-devex.tyme.com/blog/welcome-docs-as-code#why" class="hash-link" aria-label="Direct link to Why" title="Direct link to Why" translate="no">​</a></h2>
<ul>
<li class=""><strong>Version control &amp; change tracking</strong> — docs reviewed like code, via pull requests</li>
<li class=""><strong>Better developer experience</strong> — local search, offline access, fast navigation</li>
<li class=""><strong>Easier collaboration</strong> — propose changes with a PR instead of editing a wiki</li>
<li class=""><strong>Consistency</strong> — aligned with our other engineering documentation patterns</li>
</ul>
<p>This is a POC. Content migration from Confluence will follow in subsequent
tickets — for now, explore the structure and share feedback in
<code>#tymex-pipeline-devex-support</code>.</p>]]></content:encoded>
            <category>Announcement</category>
            <category>Docusaurus</category>
        </item>
    </channel>
</rss>