<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hugo on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/hugo/</link>
    <description>Recent content in Hugo on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 18 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/hugo/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted Contact Form Backends for Static Sites: Formspree vs Formtools vs OpnForm</title>
      <link>https://www.pistack.xyz/posts/2026-06-18-self-hosted-contact-form-backends-formspree-formtools-opnform/</link>
      <pubDate>Thu, 18 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-18-self-hosted-contact-form-backends-formspree-formtools-opnform/</guid>
      <description>&lt;h2 id=&#34;why-self-host-your-contact-form-backend&#34;&gt;Why Self-Host Your Contact Form Backend?&lt;/h2&gt;&#xA;&lt;p&gt;Static site generators like Hugo, Jekyll, and Eleventy have revolutionized web publishing, but they have one fundamental limitation: they can&amp;rsquo;t process form submissions. Contact forms, newsletter signups, and feedback surveys all require a server-side component to receive and store submissions. Third-party form services fill this gap, but they come with subscription costs, data privacy concerns, and vendor lock-in.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
