Nicely done! It’s super exciting and liberating once you finally start to get this working, isn’t it. 
Here are a few other points I’ve learned along with way:
-
AppleSilicon, for those using AppleSilicon, your pandoc Paths will probably be different, e.g., 1/opt/homebrew1 vs.
/user/local/bin. See: Notice for pandoc and Homebrew users upgrading to Apple M1 - steps for addressing installation error -
Retaining Headings in Word, it took me months to find the solution for this, Word, with the pandoc to Word export, does not immediately recognize the internal Word sytles. If you have a H1 or # styling in Tinderbox this style will not be properly associated with the “Heading 1” format in Word, or any other custom Word formats you might have created in your Word template, e.g., Author. To get around this. you need to wrap your headers with a div, e.g.,
<div custom-style="Heading 1"><h1>$Name</h1></div>or<div custom-style="Author"><p class="author">$Name</p></div>. My method is a bit more complicated as I have the heading numbers dynamically generated, e.g.,<div custom-style="Heading ^value($HeadingDepth)^">, to reduce the complexity of the file, which can be a bit tricky to setup but once setup you don’t need to touch it again - Markdown vs. HTML, personally, I’ve found mixing markdown and HTML to be the way to go, remember, markdown is just shorthand for HTML. In TBX templates HTML is easier, especially if you’re working with images and links, in the body of text Markdown is easier to use, especially when you’re trying to format heading and bullets.
- Dynamically numbered/formatted headings, remember, you can use action code and templates to have Tinderbox use the container structure to dynamically manage your heading 1, heading 2, heading 3 outline structure (there are several videos and meetups that cover this."
- Citation tools, Bookends works great for this process, as does other citation tools, like Zotero (you have many options.
- Citation export, If you’re using a multi-note strategy to construct your file Pandoc will generate the references and bibliography file on each note and NOT add a consolidated bibliography file at the end. To accommodate for this I’ve developed several “generator draft” strategies which creates an interim note the consolidates multiple notes into one before performing the Pandoc export. There are several approach to this to consider, especially if you’re exporting chapter sections rathe than a whole book.
- Glossaries, don’t forget that using recursive includes are great for dynamically formatting sections of an export, e.g., glossary tables vs. bulleted lists vs. how captions are set to images based on the type of citation style you’re using (all of this can be dynamically handled in templates). We’ve covered this in past meetups.
- Tables, Warning, no matter how hard you try, Word WILL NOT let you pass formatted tables from TBX through Pandoc to Word. Word strips out the HTML. The only way I’ve found to automated this is to mess with updating the Word XML post export which is an unreliable hack. I’d love to try to solve this.
- PowerPoint, in addition to exporting Word Docs, you can also use this pandoc method to export PowerPoint files. It is a bit more of set in TBX but it works.