| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Elements which are optional in the Atom feed spec should also be
optional in the templates.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Atom feed dates reported as UTC were not necessarily UTC. The entry
archetype converts from local to UTC by default, but the user may
override that behavior.
|
| |
|
|
|
|
| |
For privacy reasons, user time zones are not recorded at the moment they
are created by an archetype. Without knowing the time zone offset, the
true date is ambiguous. To correct this, all dates are converted to UTC.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
