<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Organization on Ghafoor's Personal Blog</title><link>http://ghafoorsblog.com/tags/organization/</link><description>Recent content in Organization on Ghafoor's Personal Blog</description><generator>Hugo</generator><language>en</language><managingEditor>noreply@example.com (AG Sayyed)</managingEditor><webMaster>noreply@example.com (AG Sayyed)</webMaster><copyright>Copyright © 2024-2026 AG Sayyed. All Rights Reserved.</copyright><lastBuildDate>Fri, 15 May 2026 13:20:20 +0100</lastBuildDate><atom:link href="http://ghafoorsblog.com/tags/organization/index.xml" rel="self" type="application/rss+xml"/><item><title>Configuration Support &amp; Module Organization</title><link>http://ghafoorsblog.com/courses/ags/hbstack-content/hbstack/04-hbstack-configuration/01-module/003-configuration-support/</link><pubDate>Thu, 25 Sep 2025 14:30:00 +0000</pubDate><author>noreply@example.com (AG Sayyed)</author><guid>http://ghafoorsblog.com/courses/ags/hbstack-content/hbstack/04-hbstack-configuration/01-module/003-configuration-support/</guid><description>&lt;h2 id="configuration-support--module-organization"&gt;Configuration Support &amp;amp; Module Organization&lt;/h2&gt;
&lt;p&gt;This document details how we successfully achieved &lt;strong&gt;modular configuration organization&lt;/strong&gt; for HBStack without breaking Hugo&amp;rsquo;s core functionality. We solved the challenge of separating module-specific configurations while maintaining proper site rendering and avoiding unintended multilingual site creation.&lt;/p&gt;
&lt;h2 id="-the-challenge"&gt;🎯 The Challenge&lt;/h2&gt;
&lt;p&gt;Initially, we attempted to separate HBStack module configurations into individual files to improve maintainability:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;params.blog.yaml&lt;/code&gt; - Blog module configuration&lt;/li&gt;
&lt;li&gt;&lt;code&gt;params.docs.yaml&lt;/code&gt; - Documentation module configuration&lt;/li&gt;
&lt;li&gt;&lt;code&gt;params.pwa.yaml&lt;/code&gt; - PWA module configuration&lt;/li&gt;
&lt;li&gt;&lt;code&gt;params.seo.yaml&lt;/code&gt; - SEO module configuration&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Problem&lt;/strong&gt;: Hugo interpreted these as language-specific configurations, creating separate language sites instead of module configurations, resulting in:&lt;/p&gt;</description></item></channel></rss>