<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Technical-Writing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/technical-writing/</link>
    <description>Recent content in Technical-Writing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 11 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/technical-writing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>markdownlint vs remark-lint vs Vale in 2026: The Docs Linting Stack That Ends Review Nitpicks</title>
      <link>https://www.pistack.xyz/posts/2026-11-11-docs-linting-markdownlint-remark-lint-vale/</link>
      <pubDate>Wed, 11 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-11-docs-linting-markdownlint-remark-lint-vale/</guid>
      <description>&lt;p&gt;A documentation repository with four hundred pages and six contributors has a predictable failure mode: heading levels drift, code fences lose their language tag, the same word gets spelled three different ways, and every pull request collects a dozen &amp;ldquo;can you fix the spacing&amp;rdquo; comments. None of that is a writing problem. It is a missing build step.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
