<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>content on DN4B.com: Domain Names for Business</title>
    <link>https://dn4b.com/tags/content/</link>
    <description>Recent content in content on DN4B.com: Domain Names for Business</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://dn4b.com/tags/content/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>microcontent.org</title>
      <link>https://dn4b.com/microcontent.org/</link>
      <pubDate>Wed, 17 Jun 2026 00:00:00 +0000</pubDate>
      
      <guid>https://dn4b.com/microcontent.org/</guid>
      <description>The words that decide whether software gets used are almost never in the documentation. They are on the button, in the error message, above the empty state, and somebody wrote them in four minutes.
Microcopy is now a recognised specialism with practitioners, conferences and a body of research, and it has no central resource. That is the gap.
The term microcontent is older and broader, coined in information design for the small units carrying disproportionate weight: headlines, labels, summaries, previews.</description>
    </item>
    
  </channel>
</rss>
