<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ux on Corey Daley</title><link>https://coreydaley.dev/tags/ux/</link><description>Recent content in Ux on Corey Daley</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 08 Feb 2026 19:19:33 -0500</lastBuildDate><atom:link href="https://coreydaley.dev/tags/ux/rss.xml" rel="self" type="application/rss+xml"/><item><title>A Search UI That Feels Native: Pagefind + Custom JSON Rendering</title><link>https://coreydaley.dev/posts/2026/02/pagefind-custom-search-ui/</link><pubDate>Sun, 08 Feb 2026 19:19:33 -0500</pubDate><guid>https://coreydaley.dev/posts/2026/02/pagefind-custom-search-ui/</guid><description>&lt;p&gt;The default Pagefind UI is great for quick setup, but what if you want search results that feel like they belong to your site? That&amp;rsquo;s exactly what I built for this blog. Instead of using Pagefind&amp;rsquo;s default UI with its own markup and styles, I tapped directly into the Pagefind API to pull JSON results and render them using the same post card structure used throughout the theme.&lt;/p&gt;
&lt;p&gt;The result? Search that feels completely native—same date formats, same taxonomy chips, same layout consistency. This post walks through the technical approach: loading Pagefind as a module, querying for results, and building custom rendering logic.&lt;/p&gt;
&lt;p&gt;If you&amp;rsquo;re building with Hugo or any static site generator and want full control over your search UI, this approach might inspire you. How are you handling search on your static sites?&lt;/p&gt;
&lt;p&gt;Read more at &lt;a
 href="https://coreydaley.dev/posts/2026/02/pagefind-custom-search-ui/" target="_blank" rel="noopener noreferrer"&gt;https://coreydaley.dev/posts/2026/02/pagefind-custom-search-ui/&lt;/a&gt;
&lt;/p&gt;</description></item></channel></rss>