Member-only story
Why I built a bridge between Obsidian and Hugo
Last April, when I explained why I replaced WordPress with Hugo, I wrote that publishing from Obsidian required “no export step.”
I was wrong. Or more precisely: I was paying the export step in small, invisible installments. Stripping wikilinks by hand. Deleting my private notes section before every publish. Fixing image paths. Rewriting YAML frontmatter as TOML. None of these took more than a minute — which is exactly why I tolerated them for months.
Then one evening I published an article with a [[wikilink]] still sitting in the middle of a paragraph, rendered as raw brackets for the whole world to see. That was the push I needed. I did what developers do when a manual task starts itching: I built a plugin. It's called HugoBridge, and it takes a note from my vault to a publishable Hugo page bundle in one explicit command.
The lie I told myself in April
Here’s the thing nobody tells you when you connect a knowledge vault to a static site generator: they both speak Markdown, but they speak different…
