| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
| |
Sections were the one listing kind without a feed of their own, though
the section templates already linked one whenever the output format was
configured. Add the two feed templates, modelled on the taxonomy and
term ones, and turn the format on for sections in the example site.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Nothing the theme reads was written down: the parameters, the front
matter keys, the output formats each page kind needs and the two
optional site files all had to be found by reading the templates. The
readme pointed at another repository for guidance instead.
List them, and point at the example site for a working pair of
configuration files. Also state the minimum Hugo version, which was
only recorded in theme.toml.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Google Lighthouse measures more than just page contents, so obtaining a
100/100 score isn't a certainty.
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Using Hugo's configDir is more elegant.
css/ was moved to assets so it isn't published when processing Gemini.
Files in static/ are always published. Files in assets/ are only
published when invoked in a template.
|
| |
|
