How to use Obsidian to write content for your Astro website | Hacker News Reader

How to use Obsidian to write content for your Astro website

bryanhogan.com

3 pointsbryanhogan5 comments

The obsidian‑astro‑submodule gist basically uses git to mirror a folder from your vault into an Astro project's content folder. On Windows 11 with Obsidian 1.5.9 and Node 20 I've had better luck keeping a published folder in my vault, symlinking it into src/content of my Astro site, then running astro dev to preview new posts, so a quick test could be to create a scratch note called TestPost, symlink its folder into your project, run git add && astro build and see whether that gives you a working page; does that fit your tooling or do you need a plugin?

I've tried symlinks before and wrote a whole post on how to do that as well ( https://bryanhogan.com/blog/astro-obsidian ), but I found the GitHub submodule approach better in every way.

If anyone is interested in publishing Obsidian->static site but for teams, I've been testing a git publishing [0] feature for our real-time collaboration plugin called Relay [1].

[0] https://github.com/No-Instructions/relay-git-sync

[1] https://relay.md

The first link included has nothing to do with using Obsidian to publish a site? This whole comment feels like an automated ad.

According to the Obsidian roadmap real-time collaboration will be added soon as a core feature.

For anyone interested in making their Obsidian vault into a site there are multiple options:

1. Using the official Obsidian Publish.

2. Using Quartz (or Obsidian Digital Garden)

3. Astro (custom coded, or any other static site generator, e.g. Jekyll or Hugo.

4. Astro Starlight (or any other pre-built documentation tool that can use markdown or mdx)

Hey, sorry if it felt like an ad.

I was just actively working on that project and i was excited to share it, but i see that i didn't do a good job connecting the dots.

I think we both agree that Obsidian is a best-in-class writing tool, and that Jekyll, Hugo, Astro, etc are also the best way to publish content.

Relay makes this flow really smooth for teams by attaching CRDTs to the editor to enable google-docs-like editing capabilities. The git sync app that i posted turns these merged crdts back into a git repo.

If you aren't writing in a team then it makes sense that it would feel like a bunch of extra steps.

If you *are* working in a collaborative team setting then managing git conflicts is painful overhead. I'm obviously biased, but I think it solves a real problem.

You're also right that Obsidian Sync supports non-real-time collaboration, and Obsidian has collaboration on their roadmap.

They also have a different architecture that would make automatically merging and publishing hard. I imagine you would need to make one person on the team be in charge of pushing periodically instead.

Anyway, thanks for sharing your post.

Reply on news.ycombinator.com