<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Explore Wonosobo — Engineering</title>
    <link>https://explorewonosobo.com/engineering/</link>
    <atom:link href="https://explorewonosobo.com/engineering/feed.xml"
               rel="self"
               type="application/rss+xml" />
    <description>Architecture decisions, code, performance, and security notes behind ExploreWonosobo.com.</description>
    <language>en</language>
    <lastBuildDate>Sat, 09 Aug 2025 10:00:00 +0700</lastBuildDate>
    <ttl>1800</ttl>
    <generator>ExploreWonosobo Static</generator>

    <item>
      <title>Hybrid Vertical Search for a City: Architecture, Code &amp; Trade-offs</title>
      <link>https://explorewonosobo.com/engineering/hybrid-search.html</link>
      <guid isPermaLink="true">https://explorewonosobo.com/engineering/hybrid-search.html</guid>
      <pubDate>Sat, 09 Aug 2025 09:30:00 +0700</pubDate>
      <category>Architecture</category>
      <category>Search</category>
      <category>Performance</category>
      <category>Security</category>
      <description><![CDATA[
        We built a low-ops hybrid search for a city vertical: intent router + curated verticals for high-intent queries, with Google Programmable Search fallback for breadth.
      ]]></description>
      <content:encoded><![CDATA[
        <p>We ship a pragmatic stack: an explicit <em>intent router</em> for high-intent queries and a <strong>Google Programmable Search</strong> fallback for everything else. The article includes real code (router, JSON verticals, lazy PSE), Core Web Vitals RUM, and CSP notes.</p>
        <p><a href="https://explorewonosobo.com/engineering/hybrid-search.html">Read the full article →</a></p>
      ]]></content:encoded>
      <author>info@explorewonosobo.com (Explore Wonosobo)</author>
    </item>

  </channel>
</rss>
