Some checks are pending
Auto-update PR branches / Update open PR branches (push) Waiting to run
CI / Frontend Static Quality Checks (push) Waiting to run
CI / Frontend Tests & Coverage (push) Waiting to run
CI / Rust Tests & Quality Checks (push) Waiting to run
CI / Linux build verification (push) Waiting to run
Deploy docs / Build VitePress site (push) Waiting to run
Deploy docs / Deploy to GitHub Pages (push) Blocked by required conditions
Release (Alpha) / Compute alpha version (push) Waiting to run
Release (Alpha) / Build release artifacts (push) Blocked by required conditions
Release (Alpha) / GitHub Release (alpha) (push) Blocked by required conditions
Release (Alpha) / Update docs and release pages (push) Blocked by required conditions
Source snapshot: 514ab1975951d94342ea38e64101d5a0f1c51c77
24 lines
780 B
Markdown
24 lines
780 B
Markdown
# Inbox
|
|
|
|
The Inbox is for notes that have been captured but not yet organized.
|
|
|
|
## Why It Exists
|
|
|
|
Fast capture should not require perfect structure. The Inbox gives you a place to put incomplete notes, then process them later.
|
|
|
|
The Inbox workflow is optional. Turn it off in Settings > Workflow if you prefer every note to appear organized by default.
|
|
|
|
## Organizing Inbox Notes
|
|
|
|
When reviewing the Inbox:
|
|
|
|
1. Give the note a clear H1.
|
|
2. Set its `type`.
|
|
3. Add status, dates, or URL if useful.
|
|
4. Add relationships with wikilinks or frontmatter fields.
|
|
5. Move it into a folder only if the folder adds value.
|
|
|
|
## Healthy Inbox Habit
|
|
|
|
Keep the Inbox small enough that it can be reviewed in one focused pass. Tolaria works best when capture is fast and organization is deliberate.
|