<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>site development on Publishing House</title>
    <link>https://publishinghouse.org/tags/site-development/</link>
    <description>Recent content in site development on Publishing House</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 29 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://publishinghouse.org/tags/site-development/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to Add Search to a Hugo Site</title>
      <link>https://publishinghouse.org/how-to-add-search-to-a-hugo-site/</link>
      <pubDate>Wed, 29 Apr 2026 00:00:00 +0000</pubDate>
      
      <guid>https://publishinghouse.org/how-to-add-search-to-a-hugo-site/</guid>
      <description>Hugo is fast, flexible, and opinionated in all the right ways — but it ships without built-in search. Since Hugo generates a static site, there is no server-side query engine to call. Search has to be handled either at build time, client-side in the browser, or through a third-party service. Each approach has tradeoffs worth understanding before you commit to one.
This guide covers the main options and walks through the implementation that works best for most publishing workflows.</description>
    </item>
    
  </channel>
</rss>
