DocumentationWorkflows
Rust · 0.1.0
Workflows
Turn everyday notes into a lightweight daily log, a review queue or a connected collection of ideas.
Choose a method for a real problem
These are suggested habits built from ordinary memos, tags, links and views. They are not separate application modes, background automations or promises of a complete task-management system. Pick one recurring need and try the smallest routine that addresses it.
| Your problem | Method | A useful result |
|---|---|---|
| I forget what happened during the day | Daily log | A short daily note and one review |
| Captured ideas never become actions | Capture and review | A small next-action queue |
| Useful ideas stay disconnected | Connect small ideas | Focused notes with meaningful references |
Start with a reusable note
Copy this small structure into a memo and adapt it after a few days. A question left unanswered is often more useful than extra categories. Choose the memo's actual visibility independently of its tags.
## Today
- What happened?
- What did I learn?
## Next
- [ ] One concrete action
## Question
What should I revisit?
#journalReview instead of endlessly organizing
At your next review, search one stable tag or open a saved view. Read the oldest unfinished items, choose a concrete next step, and archive material you no longer need in an active list. Add a link only when you can explain the relationship in a sentence; a large collection of tags alone will not supply that explanation.
Know the boundaries
A checklist in Markdown is content inside a note. A tag is a retrieval hint, and a view is a filter. None of them creates a scheduled reminder or changes another person's permissions. If the routine needs notifications, external task execution or a team workflow, design that integration explicitly and consult the integration guides.