<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Docmagician on Medium]]></title>
        <description><![CDATA[Stories by Docmagician on Medium]]></description>
        <link>https://medium.com/@docmagician?source=rss-e2598f96067c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xiFpdcqxsrBkhpIi4wwtiw.jpeg</url>
            <title>Stories by Docmagician on Medium</title>
            <link>https://medium.com/@docmagician?source=rss-e2598f96067c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 09:01:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@docmagician/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What if DITA Dies? Let’s talk about the docs elephant in the room]]></title>
            <link>https://medium.com/@docmagician/what-if-dita-dies-lets-talk-about-the-docs-elephant-in-the-room-7a47895fb022?source=rss-e2598f96067c------2</link>
            <guid isPermaLink="false">https://medium.com/p/7a47895fb022</guid>
            <category><![CDATA[doc-as-code]]></category>
            <category><![CDATA[technical-writing]]></category>
            <category><![CDATA[documentation]]></category>
            <category><![CDATA[dita]]></category>
            <dc:creator><![CDATA[Docmagician]]></dc:creator>
            <pubDate>Thu, 17 Apr 2025 12:06:37 GMT</pubDate>
            <atom:updated>2025-04-30T08:53:36.285Z</atom:updated>
            <content:encoded><![CDATA[<p>We don’t like to talk about it.</p><p>Not in team meetings, not in documentation stand-ups, and definitely not on public forums.</p><p>But here it is, blunt and awkward:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tDLJ72iLmcfqyhh_UJzRXQ.jpeg" /></figure><h3><strong>What if DITA dies?</strong></h3><p>Yeah, I said it.</p><p>For a long time, DITA (that’s Darwin Information Typing Architecture if you’re new here) has been the elephant in the room of structured content. Big, powerful, kind of hard to work around, and definitely not easy to ignore.</p><p>It’s modular, scalable, metadata-savvy, and localization-ready.<br> In other words, enterprise documentation’s favorite overachiever.</p><p>But lately?</p><p>Things are shifting.</p><p>Docs-as-code is gaining traction.<br> Developers are all-in on Markdown.<br> And product teams? They want fast, Git-friendly workflows that don’t need a PhD in XML.</p><p>So yeah… maybe it’s time we talk about the elephant. Before it quietly walks out of the room.</p><h3><strong>Could DITA actually shut down? Yeah, technically.</strong></h3><p>Look, DITA’s not going to die like someone’s going to pull the plug and wipe out all your content. It’ll be more of a slow fade as newer tools take over. DITA might just become less relevant over time, but a sudden shutdown? Unlikely.</p><p>Here’s how that slow fade could look behind the scenes.</p><ol><li><strong>The toolkit stops keeping up</strong><br> Everything in DITA depends on the DITA Open Toolkit. That’s the engine that turns your content into PDFs, HTML, or whatever format your company needs.<br> But what if the team behind it slows down or moves on? Maybe updates become rare or it doesn’t support newer tech. Suddenly, you’re stuck. Your publishing pipeline starts to feel fragile, and no one wants to babysit a broken XML build process on a Friday release.</li><li><strong>Your favorite tools quietly drop it</strong><br> Most of us use DITA through editors like Oxygen or XMetaL. But if those tools start focusing more on Markdown, Git, or CMS workflows (and honestly, they are), DITA becomes an afterthought. No updates, no support, maybe even a sunset notice in a few years.<br> If the editor goes, a huge chunk of your workflow goes with it.</li><li><strong>It stops playing nice with modern stacks</strong><br> These days, everything’s about Git, APIs, CI/CD, and publishing on the fly. But DITA isn’t exactly built for that world. Sure, you can make it work, but it’s not fun. When things are hard to maintain or don’t mesh well with modern systems, teams look for easier options.<br> If you can’t preview changes in GitHub, your build takes forever, or no one wants to deal with a broken conref again, yeah, people will move on.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*SKvqN9M6OLllSjw0yJx6FA.png" /></figure><p>.</p><ol><li><strong>Your content gets stuck</strong><br> Here’s the scary part, what if you’re still using DITA but the tools stop supporting it? Now you’ve got thousands of topics locked in XML, and converting them feels like a nightmare. You’re stuck managing old content while everyone else is speeding ahead with Markdown and microservices.<br> That’s when the dreaded word starts popping up: migration.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/590/1*WWhQgqn5P-GddLPlmsXgug.png" /></figure><ol><li><strong>New Writers Just Don’t Learn It</strong><br> This one’s a slow burn. New writers are learning Markdown, Git, OpenAPI, Notion, and all the docs-as-code stuff. They’re not getting trained on DITA, topic types, or ditamaps. So, fewer people know how to work with it, and the ones who do? They’re either moving up to management or switching tools too.<br> Soon enough, it’s like trying to hire someone to maintain a COBOL system. Sure, it’s possible. But easy? Not so much.</li></ol><h3><strong>How to keep your docs from getting stuck in the past</strong></h3><p>DITA might still be working fine today, but that doesn’t mean you should get too comfy. A few smart tweaks now can make sure your docs don’t turn into a legacy headache later.</p><p>Here’s what you can do to stay ahead.</p><ul><li><strong>Try lighter formats on the side</strong><br> Keep using DITA if it works, but try Markdown or other simpler formats for new content. It’s faster, Git-friendly, and easier to manage.</li><li><strong>Use tools that play well with others</strong><br> Go for tools that integrate easily with Git, APIs, and modern workflows. If your stack is flexible, switching later is way less painful.</li><li><strong>Write modular, reusable content</strong><br> Break things into chunks. Reusable content is easier to maintain — and easier to migrate when the time comes.</li><li><strong>Keep an eye on industry trends</strong><br> Stay updated on things like docs-as-code, live previews, or AI tools. It helps you make smarter choices before you’re forced to.</li><li><strong>Train new writers with future in mind</strong><br> Most new folks know Git and Markdown, not DITA. Give them tools they’re comfortable with — and build your setup around that.</li><li><strong>Have a backup plan</strong><br> You don’t need to migrate today, but it helps to know <em>how</em> you would if things change. Better safe than scrambling.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/643/1*im8v7f4rwsVClH9B1vJu8g.png" /></figure><h3>So… Should you ditch DITA?</h3><p>Not necessarily.</p><p>Let’s be clear: DITA isn’t <em>bad</em>. It’s just not the only game in town anymore.</p><p>If you’re in a highly regulated industry, need advanced localization, or have complex reuse scenarios baked into your content strategy, DITA might still be the best fit. And that’s okay. But if your team is growing fast, your product is changing constantly, or your developers are living in GitHub, it might be time to rethink.</p><p>Ask yourself:</p><ul><li>Are we choosing DITA because it’s the best tool, or because it’s the one we’ve always used?</li><li>Does our documentation process make onboarding easy or overwhelming?</li><li>Could we do 80% of what we do in DITA… in something lighter?</li></ul><p>This isn’t about jumping ship. It’s about steering before you hit an iceberg.</p><h3><strong>Final Thoughts</strong></h3><p>Whether DITA stays or fades, your docs strategy should never be static. The best teams don’t just react to change; they anticipate it.</p><p>Because in the end, it’s not about the tools.<br> It’s about keeping your content and your team moving forward.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7a47895fb022" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>