Note-taking workflow: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 13: | Line 13: | ||
* Items highlighted in blue ** could potentially use a feature in MediaWiki "Needs Attention" | * Items highlighted in blue ** could potentially use a feature in MediaWiki "Needs Attention" | ||
* Idea page with fewer than two internal links | * Idea page with fewer than two internal links | ||
* Any page with more than 5 headers can probably be split into multiple pages | |||
* Any header section with more than xx words can probably be split into multiple header sections | |||
* A list or outline with more than 20 lines can probably be split with headers | |||
Latest revision as of 12:48, 24 August 2026
This page contains notes about the benefits of having a workflow and how it will be implemented.
Benefits
The workflow helps you get the most value from your notes. It helps you easily identify opportunities of improvement.
Overview
The basic workflow is capture > organize > elaborate > connect. Capture happens once for each note, but organize, elaborate, and connect happen continuously forever.
Triggers
These are indicators that a particular note needs attention.
- Items remain on your Capture page(s) - the workflow dictates that these should be removed from Capture pages daily
- Items highlighted in blue ** could potentially use a feature in MediaWiki "Needs Attention"
- Idea page with fewer than two internal links
- Any page with more than 5 headers can probably be split into multiple pages
- Any header section with more than xx words can probably be split into multiple header sections
- A list or outline with more than 20 lines can probably be split with headers