diff options
| author | Nicholas Johnson <> | 2026-09-20 00:00:00 +0000 |
|---|---|---|
| committer | Nicholas Johnson <> | 2026-09-20 00:00:00 +0000 |
| commit | 93831052e8ba9537d47474e1f8dbf04d9eceb9b0dff214ce422fcafe1ffaecac (patch) | |
| tree | c774c1eed616eccd64e1a26fc8dac3589e7875487009b274b3f319ac54a11948 /exampleSite/content/entry/tagging.md | |
| parent | 98be685a6f839234a0ebc07c9cba001c21c5786957d3b1d627535cfa7a56c032 (diff) | |
| download | hugo-theme-journal-93831052e8ba9537d47474e1f8dbf04d9eceb9b0dff214ce422fcafe1ffaecac.tar.gz hugo-theme-journal-93831052e8ba9537d47474e1f8dbf04d9eceb9b0dff214ce422fcafe1ffaecac.zip | |
Drop whitespace trimming from HTML and XML templates
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>
Diffstat (limited to 'exampleSite/content/entry/tagging.md')
0 files changed, 0 insertions, 0 deletions
