obsidian-export VS obsidian-pandoc

Found: https://github.com/zoni/obsidian-export but hope this can be part of a single solution.

I use this obsidian-export CLI program to convert prior to pushing to my repo and it's been working pretty well. This gives me a read-only version of my notes that is accessible from devices I don't have obsidian on (work laptop, for example).

If you limit your use of third party plugins, you can always use https://github.com/zoni/obsidian-export for this as well. I originally built it for exactly this use case (but now also use it as a crucial step in my pipeline to publish content to my own website)

It came from here! https://github.com/zoni/obsidian-export

Worth noting I maintain a project which does exactly this: https://github.com/zoni/obsidian-export

I have similar folders to [Oudwin](https://www.reddit.com/user/Oudwin/)... - dm - _inbox - assets - checklist - communications - research-reference - elements - sessions Additionally, I have had reasonable success using [obsidian-export](https://github.com/zoni/obsidian-export) to export my Obsidian vault to CommonMark. From there you have more options. I then build html pages using [mdbook](https://rust-lang.github.io/mdBook/) to control the information that is revealed to players. I am playing with using [MkDocs](https://www.mkdocs.org/) to see if it offers more control/flexibility. Regardless, the /elements folder contains all the lore chunks of the world including information I keep on the PCs. The /communications and /sessions folders can contain info with links to /elements that are revealed as needed. I make heavy use of transclusion ![[CoolThingFormAnotherFolder]] to keep it a bit more elegant and some custom styles are needed to make it how it look how I wish.

I have had reasonable success using obsidian-export to export a vault to CommonMark. From there you have more options. I am using it for world-building in D&D and I then build html pages using mdbook to control the information that is revealed to players.

Shameless plug: obsidian-export. It will convert [[WikiLinks]] and ![[Embeds]] to plain Markdown (among a few other things) so you'll always have a way to go back if Obsidian doesn't work out the way you hoped.

So really you can't get what you want at all. You could try an external tool like this to export your notes to commonmark which is more widely supported. Ultimately if you are changing the path to files outside of obsidian (meaning they won't be automatically updated) you will break links. So maybe your best bet is to use wikilinks + an export tool.

First, based on https://github.com/OliverBalfour/obsidian-pandoc/wiki/Pandoc-Templates and https://bookdown.org/yihui/rmarkdown-cookbook/latex-template.html, I created a pandoc template in ~/.pandoc/templates/ and put this latex code in a mytemplate.latex file:

As an aside, if you do any sort of academic writing, the Zotero Integration + Pandoc plug-ins have been a game changer. It is quite an intense rabbit hole (at least for me as a humanities person) that took me to the command line, but one I’m glad I traveled down. In essence, it allows me to thoughtlessly create a fantastic first draft WITH an automatic bibliography…so, so nice to have.

As for markdown, it is much simpler than docx while having the basic formatting you'd need for writing. To export my markdown files to docx for web, I use the Pandoc extension, and you can also install and manage extensions and themes from within the app, so you don't need to code things in manually unless you want to add snippets, which there is plenty of help on the Obsidian forums.

There's a Pandoc plugin too, just so you know: https://github.com/OliverBalfour/obsidian-pandoc

You could use pandoc and specify the twocolumn option (please see https://stackoverflow.com/a/34809186). You could use pandoc standalone or use it through some Obsidian plugins (obsidian-pandoc, obsidian-enhancing-export)

Have you taken a look at obsidian-pandoc?

Have you checked out the Obsidian Pandoc plugin? I think it might meet your needs:

https://github.com/OliverBalfour/obsidian-pandoc

That being said standard Markdown does not provide notation for certain things, so it is somewhat up to interpretation how to convert certain features to standard Markdown.

It does look like the Pandoc plugin can combine documents by processing a master note and any related notes that are linked with the embed link syntax.