<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Flat-File on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/flat-file/</link>
    <description>Recent content in Flat-File on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 03 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/flat-file/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Flat-File CMS Comparison 2026: Statamic vs Kirby vs PluXML vs FlatPress</title>
      <link>https://www.pistack.xyz/posts/2026-10-03-flat-file-cms-statamic-kirby-pluxml-flatpress-comparison/</link>
      <pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-10-03-flat-file-cms-statamic-kirby-pluxml-flatpress-comparison/</guid>
      <description>&lt;p&gt;Your database-backed CMS is quietly becoming a liability: an extra service to patch, an extra backup to verify, an extra way for a small blog to go offline at 2 a.m. Flat-file CMS platforms throw the database away entirely — content lives in plain files on disk, and a page render is nothing more than a filesystem read. For the right project that is not a downgrade, it is a simplification. The catch is that &amp;ldquo;flat-file&amp;rdquo; spans a huge range of products: a commercial Laravel application at one end and a 200-star GPL blog engine at the other.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
