<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Local Files on UnGathered.com</title>
    <link>https://ungathered.com/tags/local-files/</link>
    <description>Recent content in Local Files on UnGathered.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 24 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://ungathered.com/tags/local-files/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>UnGathered Starts With What a Collection Should Contain</title>
      <link>https://ungathered.com/ungathered-starts-with-what-a-collection-should-contain/</link>
      <pubDate>Sat, 24 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://ungathered.com/ungathered-starts-with-what-a-collection-should-contain/</guid>
      <description>&lt;p&gt;A folder listing answers a straightforward question: which files are here? Unfortunately, it cannot tell you which expected files never arrived. That needs another source of information. Someone has to know that a product needs an inspection record, or that an article&amp;rsquo;s image should have a matching credit line. UnGathered gives those expectations a small, executable form.&lt;/p&gt;&#xA;&lt;p&gt;The first concept is the anchor. It is an existing item selected by a relative glob: products/* for product directories, for instance, or articles/*.md for article files. Each anchor carries the requirements declared for its collection. With a product directory named products/widget, a path rule such as {item}/drawing.pdf expands to products/widget/drawing.pdf. The rule states the relationship rather than searching vaguely for a similar filename.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
