www follows. The apex has to be told.
Two records. They look like a matched pair, and they are nothing of the sort.
The working notebook. Short observations, experiments, configuration discoveries, troubleshooting notes, and open questions — dated to the minute, kept rough on purpose.
Lab Notes are source material. Where a note’s experience turned into something a reader can carry outside the tool, the resulting Journal article will cite the notes beneath it. Where the record stays a record, it stays here.
Two records. They look like a matched pair, and they are nothing of the sort.
Sixteen entries in and not one of them has shown anything.
Open complete note: A screenshot tool for a machine with no screenshot tool
I sat down to add the editor settings I’d written up in JRN 26-008 and found ~/.config/zed/ sitting there — existing, correctly named, and completely empty.
Zero files.
Meanwhile AppData/Roaming/Zed/ has the settings.json I’ve apparently been editing all along, and AppData/Local/Zed/extensions/installed has five extensions I don’t remember installing individually.
Open complete note: Two config directories, and I would have edited the wrong one
I hadn’t. Reading the partial explained it in about four lines:
Open complete note: The feature I chose the theme for does not work on one post
What surprised me is that the fix isn’t a setting. It’s where the file lives.
From this:
content/posts/first-try.md
assets/my-virtual-desktop-setup.png
to this:
content/posts/first-try/index.md
content/posts/first-try/my-virtual-desktop-setup.png
That’s a page bundle, and inside one the image stops being a loose asset and becomes a page resource — reachable via .Page.Resources.Get, carrying its own front matter for alt text and caption and credit, and eligible for .Resize.
Open complete note: 1,784,655 bytes to 36,616, by moving one file
The post rendered. Right title, right date, theme styling, HTTP 200. And it appeared in no index anywhere on the site.
Open complete note: A page can render perfectly and exist nowhere
timeZone in config.Then I worked out what it’s preventing.
Open complete note: A theme that refuses to build, and why I came around to it
One command:
$ git submodule add https://github.com/jwogrady/hugo-spectrum themes/hugo-spectrum
Submodule rather than Hugo Modules, because Modules wants a go.mod and 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.
baseof.html and page.html I’d written an hour earlier were still sitting in layouts/.A project file at the same path beats the theme’s entirely. Not merged, not layered — replaced.
Open complete note: I installed the theme and the theme did not appear
Almost every Hugo tutorial says to put templates in layouts/_default/. Almost every Hugo tutorial is describing a structure that changed in 0.146.
Open complete note: Every tutorial I can find predates the directory I need
Zed’s defaults are tuned for code, which is the right call and leaves four of them wrong for what I’m actually doing in here.
Open complete note: Four editor defaults that are right for code and wrong for prose