# ux writing (blogs) — RSS Amplifier Recent posts from the 2 feeds in the RSS Amplifier directory that cover ux writing. Page: Feed: --- ## [Why I Started Doc4Docs](https://doc4docs.com/posts/20-why-i-started-doc4docs/) _2026-04-13 · Doc4Docs_ After 25 years in IT, I still see the same problem everywhere: products that deserve better documentation than they have. ## [Documentation as a Competitive Advantage](https://doc4docs.com/posts/19-documentation-as-competitive-advantage/) _2026-04-11 · Doc4Docs_ When two products are roughly equal, documentation often decides which one wins. ## [AI Tools for Technical Writers: What Actually Helps](https://doc4docs.com/posts/18-ai-tools-for-technical-writers/) _2026-04-08 · Doc4Docs_ AI can help with documentation. It can't replace the person who understands the product and the user. ## [Documentation Isn't Only for Software](https://doc4docs.com/posts/17-documentation-for-non-technical-products/) _2026-04-05 · Doc4Docs_ Every product that has users has a documentation problem. Software just makes it more visible. ## [Minimum Viable Documentation](https://doc4docs.com/posts/16-minimum-viable-documentation/) _2026-04-02 · Doc4Docs_ You don't need perfect documentation. You need enough documentation that users can succeed. ## [How Open Source Projects Handle Documentation](https://doc4docs.com/posts/15-open-source-documentation/) _2026-03-29 · Doc4Docs_ Open source documentation ranges from exceptional to nonexistent. The difference is almost never about talent. ## [UX Writing and Documentation: Where They Overlap](https://doc4docs.com/posts/14-ux-writing-and-documentation/) _2026-03-23 · Doc4Docs_ UX writing and technical writing serve different moments in a user's journey. Understanding the difference makes both better. ## [Your Changelog Is Also Documentation](https://doc4docs.com/posts/13-your-changelog-is-documentation/) _2026-03-17 · Doc4Docs_ A changelog is not a formality. It's documentation for the people who already use your product. ## [The Problem with PDF Documentation](https://doc4docs.com/posts/12-the-problem-with-pdf-documentation/) _2026-03-11 · Doc4Docs_ PDF documentation feels professional. It's also often the worst format for the people who need the information. ## [Docs-as-Code: Why Your Documentation Should Live Next to Your Code](https://doc4docs.com/posts/11-docs-as-code/) _2026-03-05 · Doc4Docs_ Treating documentation like code — with Git, pull requests, and CI/CD — changes how teams relate to it. ## [Non-Custodial Crypto Gateway (Sponsored)](https://crawlproof.com/a/le63EHM3PXpq) _2026-03-05 · **Sponsored**_ Accept multi-chain crypto, automated fee handling, and trustless escrow with real-time settlement. ## [How to Write a Good README](https://doc4docs.com/posts/10-how-to-write-a-good-readme/) _2026-02-27 · Doc4Docs_ The README is the front door of your project. Most of them are locked. ## [Technical Writing and Developer Advocacy: What's the Difference?](https://doc4docs.com/posts/09-technical-writing-vs-developer-advocacy/) _2026-02-21 · Doc4Docs_ Both roles care about documentation. They approach it from different directions. ## [Every Page Is Page One](https://doc4docs.com/posts/08-every-page-is-page-one/) _2026-02-15 · Doc4Docs_ Mark Baker's concept changed how I think about structuring documentation. Nobody starts at the beginning anymore. ## [API Documentation Done Right](https://doc4docs.com/posts/07-api-documentation-done-right/) _2026-02-09 · Doc4Docs_ API documentation has its own rules. Here's what separates the docs developers actually use from the ones they ignore. ## [What Write the Docs Taught Me About Documentation](https://doc4docs.com/posts/06-what-write-the-docs-taught-me/) _2026-02-03 · Doc4Docs_ Write the Docs is a conference and a community. After speaking there, here's what stayed with me. ## [Documentation Is a Product Feature](https://doc4docs.com/posts/05-documentation-as-a-product-feature/) _2026-01-28 · Doc4Docs_ Documentation is not the thing you do after shipping. It's part of what you ship. ## [Why Developers Hate Writing Docs (And What to Do About It)](https://doc4docs.com/posts/04-why-developers-hate-writing-docs/) _2026-01-22 · Doc4Docs_ It's not laziness. The reasons developers avoid documentation are structural, cultural, and sometimes entirely reasonable. ## [The Diataxis Framework: Four Types of Documentation](https://doc4docs.com/posts/03-diataxis-framework-explained/) _2026-01-16 · Doc4Docs_ Daniele Procida's Diataxis framework gives documentation a clear map. Here's what the four types are and why the distinction matters. ## [The Real Cost of Bad Documentation](https://doc4docs.com/posts/02-the-cost-of-bad-documentation/) _2026-01-10 · Doc4Docs_ Bad documentation has a price. It shows up in support tickets, lost users, and products that never reach their potential. ## [Documentation Is Not Dead in the AI Era](https://doc4docs.com/posts/01-documentation-is-not-dead-in-the-ai-era/) _2026-01-05 · Doc4Docs_ Every few years someone declares documentation dead. AI is the latest reason. They're wrong, and here's why. ## [Ask the crowd: AI or not (Sponsored)](https://crawlproof.com/a/iZf3CbRAnxmB) _2026-01-05 · **Sponsored**_ Get a transparent verdict from verified humans via web, RSS, or API. ## [Co-designing with AI](https://owenwillia.ms/2025/05/23/co-designing-with-ai/) _2025-05-23 · {"twitter"=\>"ow", "picture"=\>"/images/itme.jpg"} · Owen Williams_ How I redesigned my portfolio site by partnering with AI to experiment