Add .Summary as fallback for description #508
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
h-enk
approved these changes
Oct 14, 2021
There was a problem hiding this comment.
Verified (https://deploy-preview-508--doks.netlify.app/). Thanks!
adhadse
pushed a commit
to adhadse/doks
that referenced
this pull request
Sep 17, 2022
Add .Summary as fallback for description
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When the
.Descriptionof a page is not set, it's good practice useful to fallback to the Hugo-generated.Summaryvalue. See also: https://gohugo.io/variables/page/I have added the fallback to the
flexsearchdescriptions and descriptionmetatag. I briefly looked at other places where.Description is used:layouts/_default/index.jslayouts/_default/index.jsonHowever, I can't say if it makes sense to also add a fallback there, as well.