Using Obsidian to publish Standard.site records

I've previously done ,[object Object], on using Obsidian as an editor for a blog. That solution used Obsidian Sync set up in a docker container, syncing a vault, and a the 11ty static site generator looking at the vault for changes and generating the site on-the-fly. It was a bit cumbersome to set up but once I got it working, it was ,[object Object], nice. I could type in my Obsidian vault and the content on the blog would update ,[object Object],, which was cool. But, also kind of annoying as it meant drafts would be live, things like links between documents would break, and it was all just generally a bit... meh.

I've messed around with Leaflet very briefly recently. Looking into Standard.site's lexicons renewed my interest in a super easy to set up blog that I could edit from Obsidian. I realised that a simple Obsidian plugin could quite easily publish records to ATProto, creating the publication and pages within.

Enter obsidian-standard-site

This is a plugin I created to achieve a super simple workflow for blogging from Obsidian. Once installed, you can:

1. Authenticate with a bsky app password.
2. Set up a Standard.site publication from within Obsidian, or use an existing oneand import your content¹.
3. Write.
4. Publish.

The plugin automatically handles the publishing of pages and resolution of backlinks from wikilinks between published notes. You can add cover images and tags, too.

The Viewer

I've also included a very simple one-page HTML file that acts as a viewer for the publication. It has some nice features like displaying backlinks and thumbnails of the cover image, plus automatic dark/light mode switching. It comes with a simple setup script that configures everything properly.

Go check out the plugin on GitHub!

Features not yet integrated (but coming soon!)

• bskyPostRef: Linking a bsky post to a page, for interaction tracking & comment display.
• Subscribe button on viewer.
• Inlined images that aren't URLs.
• GFM footnotes and other markdown extensions.
• Better routing in the viewer: hash-based routing has limitations with shareability and link previews.

---

Footnotes

1. Note: the plugin uses raw markdown in the content field of its pages, so YMMV for compatibility with other publication sources. ↩