I installed the theme and the theme did not appear
Project templates beat theme templates at the same path — completely, not partially.
Install
-
One command:
$ git submodule add https://github.com/jwogrady/hugo-spectrum themes/hugo-spectrum -
Submodule rather than Hugo Modules, because Modules wants a
go.modand this theme doesn’t ship one. -
The submodule pins a commit, which means a checkout a year from now builds the same site as today.
-
I like that property a lot.
What I found
- Then I rebuilt and got my own handmade templates back.
- The scaffold
baseof.htmlandpage.htmlI’d written an hour earlier were still sitting inlayouts/. - Five files were quietly overriding a theme I’d just installed, and the build was perfectly happy about it.
A project file at the same path beats the theme’s entirely. Not merged, not layered — replaced.
- So deleting my own work was the install step, which is a funny thing to discover.
What I carry forward
- Any override I keep from now on is a fork of that one file.
- It stops receiving theme updates and nothing will warn me when upstream changes it underneath.
- Override as little as possible, and leave a comment in the file saying what it forked and why.
- For anyone cloning this repo —
git clone --recurse-submodules, orthemes/is empty and the build fails in a way that reads like a content bug.