We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I have slept on this.
With the addition of a params section in front matter, we get a much better separation of Hugo configuration/metadata and user metadata.
params
Me do merge in the Hugo metadata keys that's not in the user defined map. Having a merged view of this is very convenient in some situations:
.Params
.Params.summary
.Params.tags
Related
But we can and should warn (but allow that warning to be turned off) when people do this and similar:
--- title: "Foo" params: title: "Bar2" ---
Maybe not the greatest example, but is at least simple.
The text was updated successfully, but these errors were encountered:
Emit a warning that can be turned off when overwriting built-in .Para…
2e380eb
…ms values Fixes gohugoio#11941
686598f
afee781
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sorry, something went wrong.
bep
No branches or pull requests
I have slept on this.
With the addition of a
params
section in front matter, we get a much better separation of Hugo configuration/metadata and user metadata.Me do merge in the Hugo metadata keys that's not in the user defined map. Having a merged view of this is very convenient in some situations:
.Params
, e.g..Params.summary
,.Params.tags
.Related
.But we can and should warn (but allow that warning to be turned off) when people do this and similar:
Maybe not the greatest example, but is at least simple.
The text was updated successfully, but these errors were encountered: