hugo-theme-journal, branch 2026.09.19

Link the tag list from the homepage

2026-09-20T00:00:00Z

Tags reach a dead end in gemtext. The entry metadata names them, but a gemtext link must occupy a whole line, so the names are plain text and the tag pages the theme generates cannot be reached from the homepage at all. The web homepage links each entry's own tags inline, yet neither format links the tag list itself, so a site had to add it to the navigation links by hand. Add a tags section to both homepage templates, holding a single link to the taxonomy list page, and place it between the navigation links and the feed. One link rather than one per term keeps the homepage short however many tags a site accumulates, and keeps the two output formats in step. Render it only when the taxonomy page exists and has terms, so that a site whose entries carry no tags, or which disables the taxonomy kinds outright, gains no heading and no dead link. The link is labelled from a new "tagList" string rather than reusing "tags", which would have read as a link named after the heading above it. As elsewhere in the theme, the taxonomy is found by lowercasing the "tags" string, so a translated site finds its own taxonomy: an example site built in Spanish links "Lista de etiquetas" under "Etiquetas". Co-Authored-By: Claude Opus 5

Link the homepage feed from the homepage

2026-09-20T00:00:00Z

The homepage was the one listing page with a feed but no link to it, so a reader could only find it through the autodiscovery element in the document head, which the capsule has no equivalent of. Sites worked around this by adding the feed to the navigation links by hand. Add a feeds section to both homepage templates, modelled on the one the taxonomy, term and section templates carry, and place it below the navigation links and above the entry list. As on those pages, it is rendered only when the home kind lists the Atom output format, so a site that omits the format gains nothing to link. The example site's homepage gains the section in both output formats and is otherwise byte-identical, as are the pages of every other kind. Co-Authored-By: Claude Opus 5

Add Atom feeds for sections

2026-09-20T00:00:00Z

Sections were the one listing kind without a feed of their own, though the section templates already linked one whenever the output format was configured. Add the two feed templates, modelled on the taxonomy and term ones, and turn the format on for sections in the example site. Co-Authored-By: Claude Opus 5

End generated capsule pages with a newline

2026-09-20T00:00:00Z

The templates gained a final newline, but the gemtext pages they build did not: the base template trimmed its own away, so every .gmi file ended mid-line and was not a POSIX text file either. The web pages and the feeds already ended with one. Stop trimming the newline after the footer partial in the gemtext base template. The footer partial keeps its own trim marker, so that the newline is emitted once rather than twice. Every generated file in the example site, gemtext and web alike, now ends with exactly one newline, and the capsule pages are otherwise byte-identical. Co-Authored-By: Claude Opus 5

End every template file with a newline

2026-09-20T00:00:00Z

Fifteen templates ended without a final newline, so they were not text files by the POSIX definition: tools that read whole lines, including sed, wc -l, read and shells' command substitution, drop or mangle the last line, and diffs of them carry a "\ No newline at end of file" marker that hides which side changed. Add the newline. The gemtext output may not change, so the four templates whose last action is emitted verbatim into a capsule page trim it away again with "-}}". The templates that end by closing a define block need no marker, since the newline then falls outside the block and is never executed, as section.gmi and single.gmi already showed. The capsule builds byte-identical gemtext and the feeds are unchanged. Web pages gain the trailing newline their templates now have, which ends the generated HTML with an EOL too. Co-Authored-By: Claude Opus 5

Drop whitespace trimming from HTML and XML templates

2026-09-20T00:00:00Z

Whitespace has no effect on the HTML and Atom output, so the trim markers on nearly every action in those templates bought nothing and made them harder to read and to edit: a maintainer had to carry the markers along with the change. The markers are load-bearing in the gemtext templates alone, where output whitespace is the formatting. Remove them from the HTML and Atom templates. The audio partial keeps its markers, since the gemtext single template uses it too. The two markup render hooks keep theirs as well, because their output is spliced inline into prose, where the newlines an untrimmed hook emits render as a space before the punctuation that follows a link. The Atom templates compute their author and entry variables before emitting anything, so untrimmed they put blank lines ahead of the XML declaration and left every feed malformed. Emit the declaration first instead; whitespace is allowed after it but not before it. The example site builds byte-identical gemtext and content-identical feeds, and its HTML differs only by a space after a "p" start tag that the whitespace processing model drops. Co-Authored-By: Claude Opus 5

Update changelog

2026-09-20T01:19:35Z

Co-Authored-By: Claude Opus 5

Document configuration in the readme

2026-09-20T00:39:08Z

Nothing the theme reads was written down: the parameters, the front matter keys, the output formats each page kind needs and the two optional site files all had to be found by reading the templates. The readme pointed at another repository for guidance instead. List them, and point at the example site for a working pair of configuration files. Also state the minimum Hugo version, which was only recorded in theme.toml. Co-Authored-By: Claude Opus 5

Add an example site

2026-09-20T00:39:04Z

The theme shipped no runnable site and documented no configuration, so every setting it reads had to be discovered by reading the templates, and there was nothing to build against when changing them. The build failure that unset RSS limits caused would have been caught immediately by an example site. The two configuration files are the separate website and capsule configurations the readme asks for, annotated with what each setting does and which are optional. The content demonstrates entries, tags, references, a standalone page and the front matter keys that control them. Also ignore build output, which no rule previously covered. Co-Authored-By: Claude Opus 5

Add section templates

2026-09-19T23:21:32Z

Every build logged "found no layout file for html for kind section", and the section URL that Hugo generates for the entry directory was rendered as an empty page in both output formats. The warning was left for each site using the theme to work around. List the section's pages the way the term templates do, and link the section feed when the site configures one. Co-Authored-By: Claude Opus 5