obsidian-html VS obsidian-html

For me I am fine with exported bibliographies because zotero('s Better BibTeX-plugin) auto-exports to a bibtex file for me anyways, which is more consistent for myself and necessary anyways for my work with RMarkdown - Obsidian is only used for writing, I then convert obsidian-markdown to standard markdown via ObsidianHTML, and then convert to normal people's file formats via RMarkdown.

I use ObsidianHTML to convert obsidian's syntax to standard markdown. This assembles a single document by inserting transclusions and handles png embeds of format

And for those who want to torment themselves with A LOT more details: Here you go.

I am generating Rmd-files from my ObsidianMD-vault via the CL-utility ObsidianHTML, to be then knitted to whatever output formats I desire. I have been testing with image scaling and titles so far, but at least for html this works fine. However, for docx it does not, and I am not exactly sure why/how to change it.

You could pay for Obsidian publish, or you can use a free and open source tool such as Obsidian to HTML to turn your vault into a bunch of HTML files and then serve that as static content on a personal website. I personally have not used this but a friend of mine has and he thought it was pretty sweet.

* How to compile obsidian markdown? The best tool I found is obsidian-html: https://github.com/obsidian-html/obsidian-html RESULT: https://second-digital-brain.netlify.app/

A pypi package that converts an Obsidian folder to proper markdown and then that markdown to html. Can also be used to convert just markdown to an html site.

To solve this challenge, I made a small update to the converter tool. The file utils.py (find it here) performs the link generation, in the function md_link() . I updated this function to always include my /garden directory as a prefix: