@donaldmendelson and @hanno.klein: I just reported a Tablature issue to summarize my findings:
#69 Markdown - Orchestra - Markdown round trip reveals inconsistent behaviour
See you on GitHub 
Cheers, Jörg
You can add sections to markdown outside of the repository to capture your change log. Orchestra v1.0 supports a “change log” by means of the pedigree attributes (added, deprecated,…) but I do not think that is what you mean.
1 Like
With “outside” you mean a separate file?
Basically, I want to keep all information in one Markdown file – if possible.
Yes, Tablature currently only supports a single level 1 heading, sorry!
1 Like
I appreciate the time you are currently taking to test Tablature. The issue you entered is more an audit trail of your extensive test. I am afraid you will have to break it down into very specific error cases and in separate issues. They need to be easily reproducible. We do not have a software team standing by to analyse, test and fix our open-source tools, sorry again! 
1 Like
Thanks for your appreciation 
I am currently working on this together with @donaldmendelson on GitHub.