Skip to main content

Obsidian vault conventions

Notey writes standard markdown files with Obsidian-compatible wiki links.

Default folders​

Images/
Notes/
  Customers/
  Draft/
  Meetings/
  Projects/
  Topics/
People/

First-level folders under Notes become dynamic slash commands. For example, Notes/Customers enables /customer.

The setup wizard can create the fixed Customers, Projects, and Topics headings, plus child folders for entered customers, projects, and topics. Project and topic setup entries create folders only; Notey writes future markdown documents inside those folders.

Imported non-image files are stored in assets folders. Draft imports are staged under Notes/Draft/<draft-stem>.assets/; when a draft is processed they are copied beside the final note under <note-stem>.assets/ and note links are rewritten to the final vault-relative paths.

Slash commands and routing​

Inline commands at the start of draft lines control where final notes are written:

  • /topic Accounts writes or appends to a topic note.
  • /meeting writes a date-prefixed meeting note.
  • /task Follow up // tomorrow appends to Notes/tasks.md.
  • Dynamic commands such as /customer Microsoft route into matching first-level Notes folders.

When /topic follows a dynamic command, its completion list is scoped to the nearest dynamic command above it. For example, after /product Widget, /topic suggests markdown files and folders under Notes/Products/Widget, including nested entries. File suggestions append to the selected file; folder suggestions create or merge a processed note inside that folder.

Selected scoped topics use inline route syntax so Notey can keep the display title separate from the target path:

/product Widget
/topic Roadmap @ Notes/Products/Widget/roadmap.md

/topic Discovery @ Notes/Products/Widget/Discovery/

People links are stored under People. Project and topic entity notes are stored at Notes/Projects/<project>.md and Notes/Topics/<topic>.md; the matching folders created by the setup wizard are used for routing captured notes, not for entity files.

Tasks​

Notey uses Notes/tasks.md as the source of truth for the task panel. Existing readable task lines remain supported:

- [ ] Send recap (due: 2026-05-20)

When Notey creates or edits a task, it adds a stable Obsidian block id and explicit metadata:

- [ ] Send recap (due: 2026-05-20) ^notey-task-abc123
- [x] Send recap (due: 2026-05-20) (completed: 2026-05-21) ^notey-task-def456

Tasks captured from a note include a link back to that note, and Notey adds a reciprocal backlink in the source note:

- [ ] Review launch (due: 2026-05-20) (source: [[Notes/roadmap|roadmap]]) ^notey-task-abc123

Completed tasks stay in their original date section for two calendar days based on the date-only completed metadata, then move to the Completed section in the Notey panel.