I know it sounds dumb because you can already do this in Markdown like this:
---
title: yes
something: huh
---
But the reasoning for this is that some parsers might render the information alongside the text, which can lead to undesired effects. However, having the metadata alongside the markdown file would be so much better as it would ease the creation of the changelog file, and let the script of the file handle such value from the json directly, rather than having a completely separate JSON file that points to the markdown file.
I know it sounds dumb because you can already do this in Markdown like this:
But the reasoning for this is that some parsers might render the information alongside the text, which can lead to undesired effects. However, having the metadata alongside the markdown file would be so much better as it would ease the creation of the changelog file, and let the script of the file handle such value from the json directly, rather than having a completely separate JSON file that points to the markdown file.