hugo-theme-journal/layouts, branch 2025.07.27.1Hugo theme for my journal.https://git.nicholasjohnson.ch/hugo-theme-journal/atom?h=2025.07.27.12025-07-27T00:00:00ZRemove support for deprecated key "site.Author"2025-07-27T00:00:00ZNicholas Johnson2025-07-26T00:00:00Zurn:sha256:3905c06481e979f9fe9e1e89de4ae35ab62bf2b7e7c906ec6cdc10d9b9c084ac
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 system2025-07-26T00:00:00ZNicholas Johnson2025-07-26T00:00:00Zurn:sha256:9bb9989fca490bfac69ea4387ccae1e9ec3ec23cf7f47a401e241ee43562f8a3
This was the only way I could get term pages to consistently render
correctly.
Move taxonomy and term layouts to layouts/_default2025-07-24T00:00:00ZNicholas Johnson2025-07-24T00:00:00Zurn:sha256:be0d5a49d7c296118600dbc2cea43ea08576ac8f7010b1b146f742fb5f5c3c22
Hugo's template system was reimplemented in Hugo version 0.146.0.
"We [the Hugo developers] have aimed to maintain as much backward
compatibility as possible by mapping "old to new," but some reported
breakages have occurred."
Reference: https://gohugo.io/templates/new-templatesystem-overview/
The "mapping "old to new,"" is not yet documented, but moving the
taxonomy and term layouts to layouts/_default seems to be sufficient to
properly generate this theme on Hugo versions later than 0.146.0.
To retain backward compatibility with older Hugo versions, the other
recommended changes to the layouts directory are not made.
Reference: https://gohugo.io/templates/new-templatesystem-overview/#changes-to-the-layouts-folder
Add non-breaking spaces within entry tag names2025-02-06T00:00:00ZNicholas Johnsonmail@nicholasjohnson.ch2025-02-06T00:00:00Zurn:sha256:e17004fc6714b7d214aa61f43fa75f1fc9bc0ec00804e0525452cb287a81958a
The spaces in tag names must be non-breaking because tag names
split across multiple lines are visually indistinguishable from distinct
tags.
Remove commas from pageinfo tags list in html2025-02-06T00:00:00ZNicholas Johnsonmail@nicholasjohnson.ch2025-02-06T00:00:00Zurn:sha256:4134775903ccf03f8973221bd1b8c6eaf93b02b923367dd536aa79af519b6769
Spaces are more aesthetically pleasing. The Gemtext output format cannot
remove the commas because then there would be no way to distinguish tags
containing spaces from distinct tags.
Move emojis outside link text, where they belong2025-02-06T00:00:00ZNicholas Johnsonmail@nicholasjohnson.ch2025-02-06T00:00:00Zurn:sha256:7c9835d7c4413c32a091895efd34c7db56ef4c8818c89dd9e27d2d5cacfc130eAdd non-breaking spaces to improve text flow2025-02-06T00:00:00ZNicholas Johnsonmail@nicholasjohnson.ch2025-02-06T00:00:00Zurn:sha256:6ac2fc6523a8038c2b7acd268d047c3e33f5939578c1ff2e7fbdd526ba422335
The spaces directly following emojis must be non-breaking because having
emojis alone on their own line is ugly and visually confusing.
The spaces within pageinfo "segments" must be non-breaking because
splitting dates and read times across multiple lines is ugly and
visually confusing.
Move /style.css to /static/css/style.css2024-11-25T00:00:00ZNicholas Johnsonmail@nicholasjohnson.ch2024-11-25T00:00:00Zurn:sha256:c5d6c0a3a039401604f56b13cd2e97e457526560cdd520ad3c6c17acdc0d878e
It's good practice to keep static website assets isolated to their own
subdirectory.
Map ref numbers to their superscripts using dict2024-11-22T00:00:00ZNicholas Johnsonmail@nicholasjohnson.ch2024-11-22T00:00:00Zurn:sha256:1196329333e8633d57e938d697bb60b06c3370e7772e9f79737e87492a2b19f9
This removes the extra iterations over reference numbers caused by using
the replace function.
Change CSS styling for external links2024-11-08T00:00:00ZNicholas Johnsonmail@nicholasjohnson.ch2024-11-08T00:00:00Zurn:sha256:9057f651fb508edf0e0488df590ed119d08a28b5b8860c7eedd1190eb6e5f571