YAML Metadata Additions

[AramZS]

Hello! This is great work, and I wanted to note that I've already found it very useful AND integrated it into one of my own projects.

I was wondering if you'd be open to a pull request to the Markdown files in Documents that added YAML header metadata to them, like explicit titles and summaries? This would be very useful for more complex operations both in Obsidian and with other markdown processors.

I also was thinking it might make sense to break down the per-letter files so they can be fully wikilinked as files instead of files+headers in Obsidian, which would be especially useful for character management. I was thinking about building an automated script to handle this during my project's build process, but it would be pretty useful to (if I can make it work) crawl your Spell Lists file and then tag individual spell files with the casters that can use them.

These are both pretty substantial changes, so I didn't want to start work on a PR unless you'd welcome them in your project. If not, that's perfectly fine, I can do it on my own system as a build task, I just want to keep them connected up to your work here so they can receive updates.

Again, thank you for this great and very useful work!

[shap-po]

+1 that would be very helpful

[OldManUmby]

Sorry for the wait! I didn't get a notification regarding this open issue. I'll get back to you on this; just a bit busy right now. THX!

[OldManUmby]

Ok, sorry for the massive delay. Work-related stuff happened. Under closer examination of your ideas ...

First and foremost, we have to bear in mind this interpretation of the D&D SRD is designed to work for those who create full-fledged D&D game publications in both print and PDF formats; it exists so that publishers don't have to convert the poorly designed PDF distributed by Wizards. Your idea would disrupt that process by forcing those publishers to remove all the extra "code" you are proposing; I'd rather keep this as tidy as possible.

However, that doesn't mean I don't like your ideas and would like to support them fully. One solution would be to create a second interpretation for those who want more digital infrastructure added to the files. This added project would also solve some other problems here too.

So, I will begin work on a second project strictly for digital PKM files. I will let you know when that is up and running and will support your input and pull requests. I finally have a bit of time and will work on it right away. That being said, I have some minor updates coming to this original project too.

Thanks! Chat soon.