aboutsummaryrefslogtreecommitdiff
path: root/layouts/home.atom.xml
Commit message (Collapse)AuthorAge
* Drop whitespace trimming from HTML and XML templatesNicholas Johnson14 hours
| | | | | | | | | | | | | | | | | | | | | | | | | 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 <noreply@anthropic.com>
* Order feeds by publish date rather than dateNicholas Johnson18 hours
| | | | | | | | | | Every listing in the theme is built from .PublishDate, but the feeds timestamped entries with .Date and left them in Hugo's default order. An entry that set both front matter keys was therefore advertised to readers with a different date, and potentially in a different order, than it appeared in on the site. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Limit home feeds to journal entriesNicholas Johnson18 hours
| | | | | | | | | | | | The homepage lists only pages in the "entry" section, but its feeds ranged over every regular page. Standalone pages such as an about page were therefore published to subscribers while never appearing on the homepage itself. Apply the same section filter the homepage templates use, so the feed and the page it describes agree on what an entry is. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Error on generating Atom feeds without an authorNicholas Johnson18 hours
| | | | | | | | | RFC 4287 requires every feed to carry an atom:author unless all of its entries carry one. Entries here never do, and the feed-level author was emitted only when params.author was set, so any site that did not set it published feeds that no conforming validator accepts. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Fix build failure when RSS limit is unsetNicholas Johnson3 days
| | | | | | | | | | | | | Hugo's default for services.rss.limit is -1 (unlimited), and passing a negative length to "first" aborts the build with "sequence length must be non-negative". Every feed template did this unconditionally, so any site that did not explicitly set services.rss.limit failed to build at all, rather than degrading to an unlimited feed. Only apply "first" when a positive limit is configured, which is the same guard Hugo's own internal RSS template uses. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* Remove support for deprecated key "site.Author"Nicholas Johnson2025-07-27
| | | | | This Hugo theme no longer supports the Hugo versions that can utilize the key "site.Author", so this code never executes.
* Migrate fully to Hugo's new template systemNicholas Johnson2025-07-26
This was the only way I could get term pages to consistently render correctly.