This allows a frontmatter.yaml file to be included in a page folder #775
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.
any 'frontmatter.yaml` file will be merged into the page header.
Caveats with this approach:
With this approach, in the admin this will be merged in transparently and shows up as if it were in the page frontmatter itself, and then when you save, it is in fact saved back into the page.
Doing anything else differently is going to be much more complex because we'll have to handle two ways of generating header data (one for admin ignoring this file, and one for frontend). However it's not even that easy because this data is potentially cached, meaning we'll have to maintain two versions in cache, leading to possible inconsistencies.
This is a pretty advanced feature and would not be something that could be set via Admin so am not sure if this is a problem or not.
Also it is fine if you use Expert mode because that reads and saves the frontmatter in the page header directly.