Git versioning of markdown export

i don’t like the internal snapshots manager to track changes in my book.
it saves one snapshot per file, and i can’t see easily for changes and errors.

since i’m a git & markdown lover, i prefer to “export all files” as markdown… and version that folder.
the export is much better than the “sync external folder” … since it keeps the hierarchical directory structure (instead of a flat list of the sync folder)

what i just miss is:

  • if i export metadata (fundamental!) they get their own file… it woudl be much better to embed the metadata as frontmatter of the markdown file (in YAML) like all md editors do.
  • if i have a "- " list. the exported MD version is made by "* " … it would be much better to keep the “-”