This allows for constructs like:
```
{{ $filters := slice (images.GaussianBlur 8) (images.Grayscale) (images.Process "jpg q30 resize 200x") }}
{{ $img = $img | images.Filter $filters }}
```
Note that the `action` option in `images.Process` is optional (`resize` in the example above), so you can use the above to just set the target format, e.g.:
```
{{ $filters := slice (images.GaussianBlur 8) (images.Grayscale) (images.Process "jpg") }}
{{ $img = $img | images.Filter $filters }}
```
Fixes#8439
Which supports all the existing actions: resize, crop, fit, fill.
But it also allows plain format conversions:
```
{{ $img = $img.Process "webp" }}
```
Which will be a simple re-encoding of the source image.
Fixes#11483
If an environment variable (`HUGO_VERSION` in this case) is going to be same for all contexts (production, deploy-preview & branch-deploy), then there is no need to specify it for each context.
Specifying it once under [build.environment] should be enough.
From https://docs.netlify.com/configure-builds/file-based-configuration/#deploy-contexts :
"any property of a context-aware key, such as [build] or [[plugins]], will be applied to all contexts unless the same property key is present in a more specific context."
- Always include example for "with layout/type set"
- Use lowercase for "set to" examples (lookup is case sensitive)
- Consistent use of taxonomy and term
Fixesgohugoio/hugoDocs#1734
- Keeps the news section fresh
- Displays last 20 releases
- One API call per build, so we shouldn't be rate-limited
- Removes old articles
- Includes content from news section (if any), date sorted with releases
Closes#1816
Bjørn Erik Pedersen