Obsidian Authoring Workflow

The round-trip

Obsidian (edit)  →  git commit  →  GitHub push  →  Pages build  →  live URL
       ↑                                                                │
       └──────────── git pull (Obsidian Git plugin) ────────────────────┘

Daily loop

1. Open the vault in Obsidian (root of the repo).
2. Create a note with Cmd/Ctrl + N. The Templates core plugin will offer note-template.md from pages/_notes/_templates/. Picking it stamps the canonical frontmatter (title, layout, permalink, …).
3. Write freely with [[wiki-links]], ![[embeds]], callouts, and #tags. Every one of those renders 1:1 on the site (see syntax reference).
4. Drop images into the editor — Obsidian saves them under assets/images/notes/ (configured in .obsidian/app.json), which is exactly where ![[image.png]] resolves on the site.
5. Commit & push.
   • With Obsidian Git plugin: Ctrl/Cmd + P → Source control: Commit all changes → Push.
   • From the terminal: standard git add / git commit / git push.
6. GitHub Pages rebuilds automatically. Within ~1 minute the new note is live at the permalink declared in its frontmatter.

Editing existing content

• Renames are safe. Obsidian’s Always update internal links setting (alwaysUpdateLinks: true in shared config) rewrites every [[link]] pointing at the renamed file. For URL-level redirects, add the old slug to the note’s aliases: array — jekyll-redirect-from will issue an HTTP redirect from the old URL.
• Moves between collections (pages/_notes/ ↔ pages/_posts/) work, but you’ll typically want to update layout: to match the destination collection’s defaults.

Local preview

The site renders the same Obsidian features locally:

docker-compose up
# → http://localhost:4000

Notes you edit in Obsidian are picked up by Jekyll’s incremental build within ~1 second. Refresh the browser to see your changes.

Validation before pushing

Run the integration’s smoke test to catch broken wiki-links, malformed frontmatter, or a regressed wiki-index schema:

./test/test_obsidian.sh

The full theme test suite (lint, build, deployment, styling, Obsidian) runs via:

./test/test_runner.sh --verbose

Once the build is live, the graph view gives the same feedback visually: any wiki-link that no longer resolves renders as a dashed red node.

Cross-machine vault sync

Use Obsidian Git for the canonical sync — it pulls on open and prompts to commit on close. This keeps every machine using the same git history that GitHub Pages publishes from, so what you see in Obsidian is exactly what readers will see on the site.

See also

• Obsidian Vault Integration
• Getting Started with the Obsidian Vault
• Obsidian Syntax Reference
• Obsidian Graph View
• Obsidian Integration Troubleshooting
• Docker