How to Use Obsidian to Write Content for Your Astro Website
Posted4 months agoActive4 months ago
bryanhogan.comTechstory
calmpositive
Debate
0/100
ObsidianAstroContent CreationSubmodule
Key topics
Obsidian
Astro
Content Creation
Submodule
Using Obsidian to write content for Astro websites with a submodule.
Snapshot generated from the HN discussion
Discussion Activity
Light discussionFirst comment
17h
Peak period
2
66-72h
Avg / period
1.3
Key moments
- 01Story posted
Aug 23, 2025 at 2:46 AM EDT
4 months ago
Step 01 - 02First comment
Aug 23, 2025 at 7:17 PM EDT
17h after posting
Step 02 - 03Peak activity
2 comments in 66-72h
Hottest window of the conversation
Step 03 - 04Latest activity
Aug 26, 2025 at 12:25 PM EDT
4 months ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
ID: 44993835Type: storyLast synced: 11/18/2025, 12:02:41 AM
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.
[0] https://github.com/No-Instructions/relay-git-sync
[1] https://relay.md
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)
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.