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

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

hugo-theme-journal/layouts/section.html, branch main

Drop whitespace trimming from HTML and XML templates

Add section templates