Allow page-specific cover settings to override site-level settings. #185
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.
I want to have cover photos visible by default, but I have specific pages that I want to hide them on. I'd still like to specify the cover image on this page for the structured data, but I want to hide it from the standard view.
Here's the configuration I'd like to use:
Site-level
config.yml
:Specific page front-matter:
With the previous code, the site-level settings took precedence, resulting in a visible cover photo.
With this change, the page-level setting, if specified, always wins over site-level settings.
To test this, I verified each combination of these three settings, trying unset,
false
, andtrue
, and found expected results for each scenario.