Zettlr VS obsidian-export

I wanted to apply this theme (https://github.com/Zettlr/Zettlr/discussion/3211) to my Zettlr, as these preset themes are kind of an eye sore. But, while it changes the toolbar and surrounding menus, it does not apply any changes whatsoever to the editor.

> Your One-Stop Publication Workbench.

https://github.com/Zettlr/Zettlr#readme (GPLv3)

Direct link to GitHub: https://github.com/Zettlr/Zettlr/releases

I can't recommend the Zettlekasten Method enough: https://zettelkasten.de/introduction/

You can do it with index cards or you can use software to practice the method and grow your note collection. I now prefer Zettlr (https://www.zettlr.com) after using Joplin (https://joplinapp.org), which are both FOSS.

One of the core strategies of the Zettlekasten Method is to link notes to each other. That's how knowledge grows: connections and synthesis (internalization/application of the connections)

Here's a 3-year-old video on the method that serves as a good primer: https://www.youtube.com/watch?v=wFZHuWLA09M

Zettlr - Price: Free (with optional donations) Markdown editor for Mac that features a user-friendly interface and advanced features for writers.

There is https://www.zettlr.com/.

I discovered recently [logseq](https://logseq.com/) and it's beautiful. I use quite a lot Zettlr for taking notes on concepts and ideas but I have to say that logseq has become my starting point for daily, short, notes and tasks. I need to work on an integration with Zettlr however, I like the possibility of the latter to organize and connect the texts, especially convenient when writing essays.

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.