| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
| |
This makes it more visually clear where the content begins and ends.
|
| | |
|
| |
|
|
|
| |
This Hugo theme no longer supports the Hugo versions that can utilize
the key "site.Author", so this code never executes.
|
| |
|
|
|
| |
This Hugo theme no longer supports Hugo versions less than 0.123.0, so
this code never executes.
|
| | |
|
| |
|
|
|
| |
This was the only way I could get term pages to consistently render
correctly.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
| |
Semantic versioning doesn't make sense for a Hugo theme, since there is
no API to track changes for.
|
| | |
|
| |
|
|
|
|
|
| |
The maximum Hugo version cannot be documented in theme.toml because Hugo
does not support such a key:
https://github.com/gohugoio/hugo/issues/5342
|
| |
|
|
|
|
|
|
| |
"build" was effectively aliased to "_build" in Hugo version 0.123.0. So
for backward compatibility, "_build" is used for Hugo versions prior to
version 0.123.0.
Reference: https://github.com/gohugoio/hugo/commit/d0ce94219049508e45c5a7c43a281ecde7778358
|
| | |
|
| |
|
|
|
|
| |
The spaces in tag names must be non-breaking because tag names
split across multiple lines are visually indistinguishable from distinct
tags.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
| |
The compound modifier hyphen in 'X minute read' for the English language
translation was missing.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
It's good practice to keep static website assets isolated to their own
subdirectory.
|
| | |
|
| |
|
|
|
| |
This removes the extra iterations over reference numbers caused by using
the replace function.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This avoids littering the gemtext templates with regex to change the
protocol.
|
| |
|
|
| |
This avoids littering the gemtext templates with "safeHTML".
|
| | |
|
| |
|
|
|
|
|
| |
Timestamp obfuscation is a niche privacy feature which contradicts how
users expect Hugo to work. If the user desires such a feature, they can
override the theme with their own custom timestamp-obfuscating
archetypes.
|
| | |
|
| |
|
|
|
|
|
| |
The entry archetype already wipes the time of day of entries and
converts their dates to UTC, for the sake of user privacy. If the user
overrides this behavior and purposely includes times and/or time zones,
the theme should not interfere.
|
| | |
|
| | |
|
