Continuing from the previous one: the Markdown files are the source of truth — so how do they become a website?

My pipeline:

Every link is replaceable:

• Obsidian → vim, vscode, anything that edits text
• GitHub → GitLab, self-hosted Gitea
• Cloudflare → Vercel, Netlify, even your own nginx
• The whole pipeline can break — the files are still in the vault

Why not full auto-sync#

I tried mounting the Obsidian vault directly inside the git repo at first. Gave up after a week: my vault has draft fragments, dream notes, mood entries — none of which I want indexed by the site's search.

The "manual triage" step is now cp from vault/published/ to repo/content/. Ten seconds of friction in exchange for a publishing boundary I actually control.

Cadence#

Roughly one or two posts a week, sometimes three in a row, sometimes nothing for two months. The pipeline has no opinion about that.

Comments

Comments are moderated. No email, no IP collection.