obsidian-publish-mkdocs VS obsidian-git

I'm using this template https://github.com/jobindjohn/obsidian-publish-mkdocs

While I encourage supporting the Obsidian team by paying, there are ways that you can get the same features without paying.

Sync - On iOS, you can use iCloud to sync your files between your Mac and iPhone. I imagine that there are more configuration options for this on Android.

Publish - lots of different ways to deploy your notes to a site. There's one repo that helps you publish with Mkdocs [1], and I'm sure there are other tools the community has created to solve this problem.

It may not be as simple to set up as Notion, but that's the price you pay for wanting a solution to be cheap, private, and let you own your own data.

[1] https://github.com/jobindjohn/obsidian-publish-mkdocs

This is the Github repo I forked mine from which has a great readme on how to get this working: https://github.com/jobindj/obsidian-publish-mkdocs

Seems cool. I am guessing you are using a local copy of Obsidian for those generated images? There might be a way to setup a github.io page to view the rendered content without downloading anything if that's something you wanted to do. This project seems to be oriented around doing that: https://github.com/jobindj/obsidian-publish-mkdocs

The entire app is structured in a way that it seems to actively encourage users to get creative and show off innovative ideas for automation and integration. With its increasing popularity, it has gotten even easier to do things like publishing without paying a dime.

Here's a totally free way to publish your Obsidian notes.

In practice I write in Obsidian, the best thing since slice bread for me. And it was obsidian-git, running every 10 minutes or so, who was keeping my GitHub vanity metrics very green.

> Joplin is using md to.

The way it's handled can make the difference in control.

> by separating that in their DB, it's a big NO for me since it's a closed silo.

Joplin is using a popular open database with a healthy community and good tooling. It's as open as markdown. Maybe not for you, when you lack the knowledge, but markdown is similar closed for anyone not understanding filesystems and editors.

> This: https://github.com/blacksmithgu/obsidian-dataview works so wonderful for me

Good for you, but that is very low level in terms of data-handling. Dataview is really just an elaborated search, there is no good level of interaction. Datacore, the next project of the Dataview is supposed to bring this, but it's not even usable yet AFAIK. Coincidental, the Obsidian-devs are also working on that front, but nothing is finished yet.

> https://github.com/denolehov/obsidian-git and b) easy to fix since it's a text file. Gosh!

That's useless when the app itself is not working. And even worse if you are not realizing the errors early.

> Aha. I don't think so. Which authority says that?

My own experience. I've tested enough plugins over the years to know their dark corners.

> And even if It's like that, my markdown files would survive everything

The thing is, technically you are not even having proper markdown, but a fork with some extensions of Obsidian. So some features of your parts might break when switching away from Obsidian. And the reason for all this is also because markdown is lacking definitions for what obsidian-people are doing with it. Coincidentally, this seems also one of the reasons why Joplin is using a database.

> And gosh, this is a good thing!

Not if they all suck.

> Installing multiple task plugins shows that something is "broke" on the user side.

Sure, because the plugins are lacking features, its the users fault... Maybe some users have just very different levels of requirements from you.

The Obsidian team uses the "remote vault" feature[1] to collaborate on making Obsidian. Since Obsidian runs on local files you could use any shared file storage like Dropbox. If you want more granular version history, you can use Git, there's a nice plugin for it[2].

[1]: https://help.obsidian.md/Obsidian+Sync/Share+remote+vaults

[2]: https://github.com/denolehov/obsidian-git

I've been using the main Obsidian git extension, https://github.com/denolehov/obsidian-git. Took some work to set it up ergnonomically but it works great now. I enabled auto-commit and push on save, and auto-pull when you start the editor. No merge conflicts yet between two machines.

Should note I use Obsidian for a journal, so it's pretty much append-only.

I use Obsidian to create notes as Markdown files on my computer and use the Obsidian Git plugin to version control the changes via Git. The Obsidian vault in which I store my notes is stored in a folder synced using iCloud Drive.

Up to my knowledge, Obsidian GIT doesn't support merge on mobile. There is a different approach for handling those on mobile using Command Line, you can find more info in this post and this article.

Plugin: https://github.com/denolehov/obsidian-git

I am using Git for that. Here is the extension that might help. https://github.com/denolehov/obsidian-git