Nice workaround to render from .md with code included!
Seems like you’ve already got most of the pieces of this workflow in place. Regarding presentations, here are some details about how I work with Reveal.js presentations in Obsidian using Quarto. It’s quite similar to what you are doing.
Are you’re familiar with @echej’s work (qmd-as-md plugin maintainer)?
He has shared a lot of relevant stuff, like a lua filter that can convert Obsidian callouts into Quarto callouts:
- Using Wikilinks and Git/Obsidian Callouts in Quarto Markdown | Daniel Borek
- This also contains a CSS snippet that makes the Obsidian callouts look the same as the Quarto callouts.
- It also contains a lua filter that can remove the non-supported wikilink formatting.
If you just want to convert the wikilinks into markdown links, there’s several plugins that support that, like Links. You could use this in conjunction with Commander for a seamless workflow.
As for citations, these are natively supported through pandoc citekeys, so you shouldn’t need to create a script for this - unless I am misunderstanding what you meant by .bib references.
Regarding the “execute code” plugin, isn’t that a bit redundant when using Quarto, since big selling point of Quarto is exactly it’s ability to execute code when you render or preview documents? Perhaps you can clarify your workflow a bit in this regard.