<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Form Data on AI VOID</title><link>https://ai-blog.noorshomelab.dev/tags/form-data/</link><description>Recent content in Form Data on AI VOID</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 04 Dec 2025 00:00:00 +0000</lastBuildDate><atom:link href="https://ai-blog.noorshomelab.dev/tags/form-data/index.xml" rel="self" type="application/rss+xml"/><item><title>Chapter 9: HTMX Extensions: Adding Superpowers (e.g., `_hyperscript`, `json-enc`)</title><link>https://ai-blog.noorshomelab.dev/htmx-mastery-2025/htmx-extensions/</link><pubDate>Thu, 04 Dec 2025 00:00:00 +0000</pubDate><guid>https://ai-blog.noorshomelab.dev/htmx-mastery-2025/htmx-extensions/</guid><description>&lt;h2 id="chapter-9-htmx-extensions-adding-superpowers-with-_hyperscript-and-json-enc"&gt;Chapter 9: HTMX Extensions: Adding Superpowers with &lt;code&gt;_hyperscript&lt;/code&gt; and &lt;code&gt;json-enc&lt;/code&gt;&lt;/h2&gt;
&lt;p&gt;Welcome back, intrepid web developer! So far, we&amp;rsquo;ve seen how HTMX empowers you to build dynamic, interactive web applications using just HTML. It&amp;rsquo;s pretty amazing how much you can achieve without writing a single line of client-side JavaScript, right?&lt;/p&gt;
&lt;p&gt;But what if you encounter a situation where you need a &lt;em&gt;little&lt;/em&gt; bit of client-side logic, or your backend expects data in a specific format that HTMX doesn&amp;rsquo;t handle by default? Do we throw in the towel and reach for a full-blown JavaScript framework? Absolutely not! This is where HTMX extensions come to the rescue, giving your HTMX-powered applications even more superpowers.&lt;/p&gt;</description></item></channel></rss>