<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Doc4Docs</title><description>Every product deserves great documentation.</description><link>https://doc4docs.com/</link><item><title>Why I Started Doc4Docs</title><link>https://doc4docs.com/posts/20-why-i-started-doc4docs/</link><guid isPermaLink="true">https://doc4docs.com/posts/20-why-i-started-doc4docs/</guid><description>After 25 years in IT, I still see the same problem everywhere: products that deserve better documentation than they have.</description><pubDate>Mon, 13 Apr 2026 10:00:00 GMT</pubDate></item><item><title>Documentation as a Competitive Advantage</title><link>https://doc4docs.com/posts/19-documentation-as-competitive-advantage/</link><guid isPermaLink="true">https://doc4docs.com/posts/19-documentation-as-competitive-advantage/</guid><description>When two products are roughly equal, documentation often decides which one wins.</description><pubDate>Sat, 11 Apr 2026 10:00:00 GMT</pubDate></item><item><title>AI Tools for Technical Writers: What Actually Helps</title><link>https://doc4docs.com/posts/18-ai-tools-for-technical-writers/</link><guid isPermaLink="true">https://doc4docs.com/posts/18-ai-tools-for-technical-writers/</guid><description>AI can help with documentation. It can&apos;t replace the person who understands the product and the user.</description><pubDate>Wed, 08 Apr 2026 10:00:00 GMT</pubDate></item><item><title>Documentation Isn&apos;t Only for Software</title><link>https://doc4docs.com/posts/17-documentation-for-non-technical-products/</link><guid isPermaLink="true">https://doc4docs.com/posts/17-documentation-for-non-technical-products/</guid><description>Every product that has users has a documentation problem. Software just makes it more visible.</description><pubDate>Sun, 05 Apr 2026 10:00:00 GMT</pubDate></item><item><title>Minimum Viable Documentation</title><link>https://doc4docs.com/posts/16-minimum-viable-documentation/</link><guid isPermaLink="true">https://doc4docs.com/posts/16-minimum-viable-documentation/</guid><description>You don&apos;t need perfect documentation. You need enough documentation that users can succeed.</description><pubDate>Thu, 02 Apr 2026 10:00:00 GMT</pubDate></item><item><title>How Open Source Projects Handle Documentation</title><link>https://doc4docs.com/posts/15-open-source-documentation/</link><guid isPermaLink="true">https://doc4docs.com/posts/15-open-source-documentation/</guid><description>Open source documentation ranges from exceptional to nonexistent. The difference is almost never about talent.</description><pubDate>Sun, 29 Mar 2026 10:00:00 GMT</pubDate></item><item><title>UX Writing and Documentation: Where They Overlap</title><link>https://doc4docs.com/posts/14-ux-writing-and-documentation/</link><guid isPermaLink="true">https://doc4docs.com/posts/14-ux-writing-and-documentation/</guid><description>UX writing and technical writing serve different moments in a user&apos;s journey. Understanding the difference makes both better.</description><pubDate>Mon, 23 Mar 2026 10:00:00 GMT</pubDate></item><item><title>Your Changelog Is Also Documentation</title><link>https://doc4docs.com/posts/13-your-changelog-is-documentation/</link><guid isPermaLink="true">https://doc4docs.com/posts/13-your-changelog-is-documentation/</guid><description>A changelog is not a formality. It&apos;s documentation for the people who already use your product.</description><pubDate>Tue, 17 Mar 2026 10:00:00 GMT</pubDate></item><item><title>The Problem with PDF Documentation</title><link>https://doc4docs.com/posts/12-the-problem-with-pdf-documentation/</link><guid isPermaLink="true">https://doc4docs.com/posts/12-the-problem-with-pdf-documentation/</guid><description>PDF documentation feels professional. It&apos;s also often the worst format for the people who need the information.</description><pubDate>Wed, 11 Mar 2026 10:00:00 GMT</pubDate></item><item><title>Docs-as-Code: Why Your Documentation Should Live Next to Your Code</title><link>https://doc4docs.com/posts/11-docs-as-code/</link><guid isPermaLink="true">https://doc4docs.com/posts/11-docs-as-code/</guid><description>Treating documentation like code — with Git, pull requests, and CI/CD — changes how teams relate to it.</description><pubDate>Thu, 05 Mar 2026 10:00:00 GMT</pubDate></item><item><title>How to Write a Good README</title><link>https://doc4docs.com/posts/10-how-to-write-a-good-readme/</link><guid isPermaLink="true">https://doc4docs.com/posts/10-how-to-write-a-good-readme/</guid><description>The README is the front door of your project. Most of them are locked.</description><pubDate>Fri, 27 Feb 2026 10:00:00 GMT</pubDate></item><item><title>Technical Writing and Developer Advocacy: What&apos;s the Difference?</title><link>https://doc4docs.com/posts/09-technical-writing-vs-developer-advocacy/</link><guid isPermaLink="true">https://doc4docs.com/posts/09-technical-writing-vs-developer-advocacy/</guid><description>Both roles care about documentation. They approach it from different directions.</description><pubDate>Sat, 21 Feb 2026 10:00:00 GMT</pubDate></item><item><title>Every Page Is Page One</title><link>https://doc4docs.com/posts/08-every-page-is-page-one/</link><guid isPermaLink="true">https://doc4docs.com/posts/08-every-page-is-page-one/</guid><description>Mark Baker&apos;s concept changed how I think about structuring documentation. Nobody starts at the beginning anymore.</description><pubDate>Sun, 15 Feb 2026 10:00:00 GMT</pubDate></item><item><title>API Documentation Done Right</title><link>https://doc4docs.com/posts/07-api-documentation-done-right/</link><guid isPermaLink="true">https://doc4docs.com/posts/07-api-documentation-done-right/</guid><description>API documentation has its own rules. Here&apos;s what separates the docs developers actually use from the ones they ignore.</description><pubDate>Mon, 09 Feb 2026 10:00:00 GMT</pubDate></item><item><title>What Write the Docs Taught Me About Documentation</title><link>https://doc4docs.com/posts/06-what-write-the-docs-taught-me/</link><guid isPermaLink="true">https://doc4docs.com/posts/06-what-write-the-docs-taught-me/</guid><description>Write the Docs is a conference and a community. After speaking there, here&apos;s what stayed with me.</description><pubDate>Tue, 03 Feb 2026 10:00:00 GMT</pubDate></item><item><title>Documentation Is a Product Feature</title><link>https://doc4docs.com/posts/05-documentation-as-a-product-feature/</link><guid isPermaLink="true">https://doc4docs.com/posts/05-documentation-as-a-product-feature/</guid><description>Documentation is not the thing you do after shipping. It&apos;s part of what you ship.</description><pubDate>Wed, 28 Jan 2026 10:00:00 GMT</pubDate></item><item><title>Why Developers Hate Writing Docs (And What to Do About It)</title><link>https://doc4docs.com/posts/04-why-developers-hate-writing-docs/</link><guid isPermaLink="true">https://doc4docs.com/posts/04-why-developers-hate-writing-docs/</guid><description>It&apos;s not laziness. The reasons developers avoid documentation are structural, cultural, and sometimes entirely reasonable.</description><pubDate>Thu, 22 Jan 2026 10:00:00 GMT</pubDate></item><item><title>The Diataxis Framework: Four Types of Documentation</title><link>https://doc4docs.com/posts/03-diataxis-framework-explained/</link><guid isPermaLink="true">https://doc4docs.com/posts/03-diataxis-framework-explained/</guid><description>Daniele Procida&apos;s Diataxis framework gives documentation a clear map. Here&apos;s what the four types are and why the distinction matters.</description><pubDate>Fri, 16 Jan 2026 10:00:00 GMT</pubDate></item><item><title>The Real Cost of Bad Documentation</title><link>https://doc4docs.com/posts/02-the-cost-of-bad-documentation/</link><guid isPermaLink="true">https://doc4docs.com/posts/02-the-cost-of-bad-documentation/</guid><description>Bad documentation has a price. It shows up in support tickets, lost users, and products that never reach their potential.</description><pubDate>Sat, 10 Jan 2026 10:00:00 GMT</pubDate></item><item><title>Documentation Is Not Dead in the AI Era</title><link>https://doc4docs.com/posts/01-documentation-is-not-dead-in-the-ai-era/</link><guid isPermaLink="true">https://doc4docs.com/posts/01-documentation-is-not-dead-in-the-ai-era/</guid><description>Every few years someone declares documentation dead. AI is the latest reason. They&apos;re wrong, and here&apos;s why.</description><pubDate>Mon, 05 Jan 2026 10:00:00 GMT</pubDate></item></channel></rss>