Keeping Markdown Formatting Intact When Obsidian Syncs to Typecho

I’m genuinely happy with the little Obsidian-based writing setup I’ve built. Obsidian’s frictionless writing experience means I can jot things down anywhere — at work, at home, on the move — and then, whenever I have time, tidy the notes up and publish them by category through a background file-sync process.

Multi-platform sync

#

1. Blog folder — drop an article in here, and a Python script running on my home NAS automatically syncs it to my blog.
2. DayOne folder — drop it here, and it publishes automatically into the DayOne app, for private storage.
3. Media folder — drop it here, and the Markdown file gets converted into a video, ready to publish across various platforms.

The one imperfection

#

The thing that kept bugging me: once a Markdown file synced over to Typecho, the Markdown-aware editor would fill up with a wall of raw HTML — making it basically impossible to go back and edit the post on the site itself.

The fix

#

Today, while setting up a visitor-tracking plugin on the site, I stumbled onto a setting that controls whether content submitted via the XML-RPC interface keeps its Markdown formatting instead of being converted to HTML. Flipping that setting solved the problem completely — the content is much tidier now.

Takeaway

#

Whether it’s private notes or public posts, Obsidian and this sync setup let me manage and publish content far more efficiently. With the “can’t cleanly re-edit synced posts” problem solved, I can finally let that particular obsession go.