We are going to release Hugo 0.25 today, and pulling in lots of unknown and untested changes is a bad idea.
This reverts commit d2c24baafee2e7ee752aeb53fb5c10a633e43d43.
f3c88b08 Add warning on GitInfo and Shallow Clones
fa5be591 Make the two common Taxonomy templates explicit
4a81c507 Update pull request link in showcase.html
f751e57a Update christianmendoza.me in the showcase
d582419b Remove commit message prefix from showcase addition guide
d12791cf Fix path for screenshot in showcase addition guide
e487b916 Add invincible.site to the showcase
c85cfccf Update guide for showcase additions
c44b31c1 Fix spelling
dc10d7f6 Add slightly better GitHub install description
2611980f Revert "Add workaround to Fetch from GitHub documentation"
b2e56907 Fix Git commit link in footer
b025a638 Regenerate commands docs for v0.24.1
0741ad08 Update README.md
942d130a Add branch info to README
e8c36390 Set hugoDocs/master to 0.24.1
c4e21471 Add workaround to Fetch from GitHub documentation
db0a3c08 Fix typo in release note
git-subtree-dir: docs
git-subtree-split: f3c88b081022c945f010cdbfcd25e0008e0c3f5b
https://gohugo.io/taxonomies/overview/ introduces the definitions 'Term' as a Key within that taxonomy.
The filename Hugo accepts for Taxonomy terms can be confusing:
SINGULAR.terms.html -> Renders at /SINGULAR/
SINGULAR.html -> Renders at /SINGULAR/TERM/
This applies to both regular templates and shortcodes. So, if the site language is French and the output format is AMP, this is the (start) of the lookup order for the home page:
1. index.fr.amp.html
2. index.amp.html
3. index.fr.html
4. index.html
5. ...
Fixes#3360
This enables `AND` (`intersect`) and `OR` (`union`) filters when combined with `where`.
Example:
```go
{{ $pages := where .Site.RegularPages "Type" "not in" (slice "page" "about") }}
{{ $pages := $pages | union (where .Site.RegularPages "Params.pinned" true) }}
{{ $pages := $pages | intersect (where .Site.RegularPages "Params.images" "!=" nil) }}
```
The above fetches regular pages not of `page` or `about` type unless they are pinned. And finally, we exclude all pages with no `images` set in Page params.
Fixes#3174
From now on we
* Deploy from master
* Anything related to Next Hugo goes into the dev branch
* Changes in hugo/docs will, in general, be merged once every release, but can be manually merged/cherry picked
* All contributions that is not tightly coupled with code changes, should be made directly to hugoDocs
* But we also merge PRs into hugo/docs, but preferably changes that is related to the code in the PR itself
The stable branch will be removed, so we now have 2 branches: master (current Hugo) and dev (next Hugo).
Closes#22
