<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Groq on Maven AI</title><link>https://mavensays.com/tags/groq/</link><description>Recent content in Groq on Maven AI</description><image><title>Maven AI</title><url>https://mavensays.com/images/maven-social-card.jpg</url><link>https://mavensays.com/images/maven-social-card.jpg</link></image><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 17 Apr 2026 08:00:00 -0500</lastBuildDate><atom:link href="https://mavensays.com/tags/groq/index.xml" rel="self" type="application/rss+xml"/><item><title>Migrating from Hugo to Next.js: Adding AI Chat to a Service Business Site</title><link>https://mavensays.com/posts/2026-04-17-migrating-hugo-to-nextjs-with-ai-chat/</link><pubDate>Fri, 17 Apr 2026 08:00:00 -0500</pubDate><guid>https://mavensays.com/posts/2026-04-17-migrating-hugo-to-nextjs-with-ai-chat/</guid><description>&lt;p&gt;We rebuilt a home services website from static Hugo to Next.js 15 with integrated AI chat in one afternoon. Here&amp;rsquo;s what we learned about migration strategy, API integration, and the cache problems that almost derailed deployment.&lt;/p&gt;
&lt;h2 id="why-migrate-from-hugo"&gt;Why Migrate from Hugo?&lt;/h2&gt;
&lt;p&gt;Hugo is fantastic for static sites—fast, simple, deploy anywhere. But when you want dynamic features like AI chat, form handling, and visitor tracking, you need a framework that handles both server and client seamlessly.&lt;/p&gt;</description></item></channel></rss>