Hugo 0.65 generalizes how a page is packaged and published to be applicable to any page. This should solve some of the most common issues we see people ask and talk about on the issue tracker and on the forum.
New in Hugo Core
Any branch node can now bundle resources (images, data files etc.), even the taxonomy nodes (e.g. /categories).
List pages (sections and the home page) can now be added to taxonomies.
The front matter fields that control when and if to publish a piece of content (draft, publishDate, expiryDate) now also works for list pages, and is recursive.
We have added a new _build front matter keyword to provide fine-grained control over page publishing. The default values:
_build:# Whether to add it to any of the page collections.# Note that the page can still be found with .Site.GetPage. list:true# Whether to render it. render:true# Whether to publish its resources. These will still be published on demand,# but enabling this can be useful if the originals (e.g. images) are# never used. publishResources:true
Note that all front matter keywords can be set in the cascade on a branch node, which would be especially useful for _build.
We have also upgraded to the latest LibSass (v3.6.3). Nothing remarkable functional new here, but it makes Hugo ready for the upcoming Dart Backport.
And finally, we have added a GetTerms method on Page, making listing the terms defined on this page in the given taxonomy much simpler:
The new features listed above required a structural simplification, and we do watch our weight when doing this. And the benchmarks show that Hugo should, in general, be slightly faster. This is especially true if you’re using taxonomies, and the partial rebuilding on content changes should be considerably faster.
This release represents 34 contributions by 6 contributors to the main Hugo code base.@bep leads the Hugo development with a significant amount of contributions, but also a big shoutout to @satotake, @QuLogic, and @JaymoKang for their ongoing contributions.
And a big thanks to @digitalcraftsman and @onedrawingperday for their relentless work on keeping the themes site in pristine condition and to @davidsneighbour and @kaushalmodi for all the great work on the documentation site.
Many have also been busy writing and fixing the documentation in hugoDocs,
which has received 7 contributions by 4 contributors. A special thanks to @coliff, @bep, @tibnew, and @nerg4l for their work on the documentation site.