obsidian-publish-mkdocs VS obsidian-releases

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.

The closest editor that follows our first principle is Obsidian editor:

The solution was already installed on both my computer and my phone: Obsidian.

> why does open source need to "win"

Open source does not need to win.

But your ability to be in control of your computer needs to be preserved. A proprietary fridge cannot control your diet, while a proprietary App Store can control what software you install on YOUR phone (unless you live in EU, hello DMA!). The tail wags the dog, so to speak. Proprietary software has also been shown to break user workflows or remove functions in an update while leaving users with no choice whatsoever.

One alternative to having open source win is to ensure software must come with a robust warranty and other assurances you expect from the things you buy. EU's CRA will make software vulnerabilities in WiFi routers covered by warranty, for example.

You can also ensure robust and interoperable data storage options. For example, https://obsidian.md/ stores all notes in Markdown, not holding the data hostage in case users will not like how future versions will work. GDPR actually has a provision for data portability (Art. 20), but it does not seem to have a requisite effect on the industry yet.

And until the above issues are solved, open source remains the best way to ensure that a software tail cannot wag your computer dog.

[2] https://obsidian.md/

So I've had my fair share of personal websites and blogs. I have built them on stacks ranging from the most basic HTML and CSS, to hosted frameworks like Wordpress and Laravel, to the more modern single page applications built in Vue and React. For a simple content blog I think you can't go wrong with a Static Site Generator though. These days I am almost exclusively writing everything in Obsidian. Which is great because its all in standard markdown format. This allows for a really neat and easy content publishing workflow.

Consider making an Obsidian[^1] plugin, or writing to Obsidian-compatible Markdown files :)

[^1]: https://obsidian.md/

Obsidian is a writing application created to allow for offline / private note taking in markdown format, in an interface that looks a lot like our regular programming IDE. It is very flexible, with a good collection of community plugins that you can use to customize Obsidian to your heart contents.

Obsidian support via our Obsidian Plugin