8739805f99
Some checks failed
Auto-update PR branches / Update open PR branches (push) Has been cancelled
CI / Frontend Static Quality Checks (push) Has been cancelled
CI / Frontend Tests & Coverage (push) Has been cancelled
CI / Rust Tests & Quality Checks (push) Has been cancelled
CI / Linux build verification (push) Has been cancelled
Release (Alpha) / Compute alpha version (push) Has been cancelled
Release (Alpha) / Build release artifacts (push) Has been cancelled
Release (Alpha) / GitHub Release (alpha) (push) Has been cancelled
Release (Alpha) / Update docs and release pages (push) Has been cancelled
Deploy docs / Build VitePress site (push) Has been cancelled
Deploy docs / Deploy to GitHub Pages (push) Has been cancelled
23 lines
676 B
Markdown
23 lines
676 B
Markdown
# Capture A Note
|
|
|
|
Source: guides/capture-a-note.md
|
|
URL: /guides/capture-a-note
|
|
|
|
# Capture A Note
|
|
|
|
Use capture when you need to get an idea into the vault before you know where it belongs.
|
|
|
|
## Steps
|
|
|
|
1. Press `Cmd+N` on macOS or `Ctrl+N` on Windows and Linux.
|
|
2. Write a clear H1.
|
|
3. Add the rough content.
|
|
4. Leave structure for later if you are still thinking.
|
|
|
|
## Capture Well
|
|
|
|
Prefer a useful title over a perfect taxonomy. You can add type, status, and relationships during inbox review.
|
|
|
|
## When To Add Structure Immediately
|
|
|
|
Add structure while capturing when the note's type or relationships are already obvious. Otherwise, capture the idea first and organize it later. |