-
-
Notifications
You must be signed in to change notification settings - Fork 8k
Closed
Description
I will update the docs (promise!), but here are a list of the main changes/fixes in this release. Also see the referenced issues.
- 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.
draft
,publishDate
,expiryDate
etc. now also works for list pages, and is recursive.- New
_build
meta keyword in front matter. SeeBuildConfig
below.headless
still works, but this is more general as it works for any page and is obviously more flexible. Can, of course, be set in acascade
block. SettingPublishResources=false
will turn off auto-publishing of bundled resources (e.g. image originals). .GetPage "members.md"
(thePage
method) will now only do relative lookups, which is what most people would expect.- A slight change of how disableKinds for regular pages: They will not be rendered on its own, but will be added to the site collections.
- We have upgraded to the latest
LibSass
(v3.6.3). Nothing remarkable functional new here, but it makes Hugo ready for the upcoming Dart Backport. - https://gohugo.io/commands/hugo_mod/#see-also
Some relevant fixed issues: Improve _index.md vs draft #6312 disableKind for Page should still add regular pages to the page collections #6087 Work in progress: Unify disableKinds behaviour #6738 Add nolist and norender #6412 headlessbundle.OutputFormats returns one item #6743 Allow scheduling of section pages (_index.md) #6875 Page's .GetPage "ambiguous" message when child is drafted #6034 Make "duplicate menu entry" a warning #6902 Allow taxonomy nodes to bundle resources #6173 List pages not added to taxonomies #6590
type BuildConfig struct {
// Whether to add it to any of the page collections.
// Note that the page can still be found with .Site.GetPage.
List bool // Default true
// Whether to render it.
Render bool // Default 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 bool // Default true
}
The above would fits into a content file with YAML front matter:
---
title: Nothing
_build:
list: false
render: false
publishResources: false
---
pamubay, davidsneighbour and maikimaiki and parthopdas