Obsidian Workspace (Placeholder)
How I structure notes, templates, and plugins in Obsidian.
A tour of my current Obsidian vault — folder layout, daily note workflow, plugin lineup, and the sync strategy that keeps nothing lost.

Quick Stats
Obsidian Workspace
The vault has been running continuously since January 2023 — this write-up is a snapshot of the current state. The structure has evolved a lot; I've documented the reasoning behind each major change.
I tried many note-taking systems before Obsidian clicked: linear documents felt too rigid, Notion databases too heavy. Obsidian sits in the right spot: plain Markdown files I own, enough structure to find things, and enough flexibility to let structure emerge.
Vault goals
Three rules that guide every structural decision:
- Everything searchable — if I can't find it in under 10 seconds, it's not worth having.
- Capture first, organise later — friction at capture time kills the habit.
- Backlinks over hierarchy — deep folder trees are a trap; let the graph surface relationships.
Folder layout

vault/
├── 00-Inbox/ ← everything lands here first
├── 10-Projects/ ← one folder per active project
├── 20-Areas/ ← ongoing responsibilities (health, finances, career)
├── 30-Resources/ ← reference material, research, books
├── 40-Archive/ ← completed projects, stale notes
└── 99-Meta/ ← templates, config notes, this structure doc
The 00-Inbox folder is the relief valve. Notes go in raw, get processed weekly into their permanent home during a Friday review.
Why not tags for top-level organisation?
Tags are great for cross-cutting concerns (#to-review, #reference, #person) but poor as the primary navigation structure. Folders answer "where am I?" immediately; tags answer "what kind of thing is this?" — both have a role.
Daily note workflow
Every morning a Templater-generated note opens automatically:
The dataview block pulls open tasks from all active projects that are due today. I don't maintain a separate task system — tasks live near the project note that created them and surface here automatically.
Plugin lineup
| Plugin | Role |
|---|---|
| Dataview | SQL-like queries on note metadata for dashboards and task lists |
| Templater | Dynamic templates with JavaScript expressions |
| Excalidraw | Embedded diagrams and visual notes |
| Calendar | Weekly/monthly calendar view linked to daily notes |
| Periodic Notes | Opens daily/weekly/monthly notes from the calendar |
| Linter | Auto-formats frontmatter and fixes list spacing on save |
| Advanced URI | Deep-links into specific notes from other apps |
| File Path Note | Syncs note title with filename to prevent drift |
The core principle: every plugin must earn its place. I audit the list every three months and remove anything that hasn't been used.
Templater example
A project note template that auto-populates metadata and creates a linked tasks note:
<%*
const title = await tp.system.prompt("Project name")
const slug = title.toLowerCase().replace(/ /g, "-")
tR += `---
title: ${title}
status: active
created: <% tp.date.now("YYYY-MM-DD") %>
---
## Goals
## Tasks
[[${slug}-tasks]]
## Notes
`
await tp.file.rename(slug)
%>
Sync setup
The vault lives in a folder synced by Syncthing across my desktop, laptop, and a VPS. Obsidian Sync is expensive for what it is; Syncthing is free and faster. The .obsidian config folder is included so plugins and themes stay in sync too.
Using inline code for the conflict-resolution rule: if Syncthing flags a conflict, the .sync-conflict-* file is always the older version — delete it, keep the main file.
Notes are compressed thinking. The vault is less about storage and more about making space to think clearly.
Have thoughts?
Curious what others see or think
Feel free to reach out or leave feedback
Share FeedbackPrefer email? joshuatjhie@pm.me