<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Problems-and-Questions on matt2ology Tech Journal and Blog</title><link>https://matt2ology.github.io/categories/problems-and-questions/</link><description>Recent content in Problems-and-Questions on matt2ology Tech Journal and Blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 20 Mar 2026 02:22:47 -0700</lastBuildDate><atom:link href="https://matt2ology.github.io/categories/problems-and-questions/index.xml" rel="self" type="application/rss+xml"/><item><title>How Do I Structure a Hugo Blog with Nested Submodules?</title><link>https://matt2ology.github.io/blog/how-to-implement-multiple-and-nested-submodules/</link><pubDate>Fri, 20 Mar 2026 02:22:47 -0700</pubDate><guid>https://matt2ology.github.io/blog/how-to-implement-multiple-and-nested-submodules/</guid><description>&lt;h2 id="how-to-implement-multiple-and-nested-submodules"&gt;&lt;a href="#how-to-implement-multiple-and-nested-submodules" class="header-anchor"&gt;&lt;/a&gt;How to implement multiple and nested submodules
&lt;/h2&gt;&lt;p&gt;I don&amp;rsquo;t know&amp;hellip;&lt;/p&gt;
&lt;p&gt;I have a repository that uses nested submodules. I want to make sure they all work where &lt;code&gt;content&lt;/code&gt; is a submodule to the main project repo, but &lt;code&gt;content&lt;/code&gt; has a submodule of its own &lt;code&gt;journal&lt;/code&gt;. Both &lt;code&gt;content&lt;/code&gt; and &lt;code&gt;journal&lt;/code&gt; are private repos to the main project repo.&lt;/p&gt;
&lt;p&gt;Where the &lt;code&gt;content&lt;/code&gt; repo to &lt;strong&gt;manage its own submodule (&lt;code&gt;journal&lt;/code&gt;) independently&lt;/strong&gt; and &lt;strong&gt;not have the &lt;code&gt;journal&lt;/code&gt; submodule tracked by the main repo&lt;/strong&gt;. That is &lt;code&gt;content&lt;/code&gt; repo to control its own submodules, but the main repo should only track &lt;code&gt;content&lt;/code&gt; as a submodule, without the nested submodule (&lt;code&gt;journal&lt;/code&gt;) being tracked directly by the main repo.&lt;/p&gt;
&lt;p&gt;All together:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Main repo&lt;/strong&gt; tracks &lt;code&gt;content&lt;/code&gt; as a submodule.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code&gt;content&lt;/code&gt; repo&lt;/strong&gt; contains its own submodule &lt;code&gt;journal&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Main repo does not track the &lt;code&gt;journal&lt;/code&gt; submodule directly.&lt;/li&gt;
&lt;/ul&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;+---.github
| \---workflows
+---archetypes
+---content (submodule)
| +---.github
| | \---workflows
| +---.obsidian
| +---archives
| +---atomic
| +---blog
| +---collections
| +---highlights
| +---journal (submodule)
| +---literature
| +---search
| \---templates
+---layouts
| +---shortcodes
| +---_markup
| \---_partials
| +---article
| \---obsidian
\---themes
 \---hugo-theme-stack (submodule)
&lt;/code&gt;&lt;/pre&gt;</description></item></channel></rss>