diff options
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 38 |
1 files changed, 22 insertions, 16 deletions
@@ -41,7 +41,7 @@ The config bootstraps packages with built-in `package.el` and uses `use-package` The current setup uses these packages and built-in modules: -- `org` and `org-capture` for agenda, capture, daily notes, and the literate configuration itself. +- `org` and `org-capture` for agenda, journal capture, and the literate configuration itself. - `denote` for durable notes, naming, keywords, and linking. - `git-auto-commit-mode` for optional automatic commits inside `~/org` when enabled by directory-local settings. - `vertico` for minibuffer completion UI. @@ -56,7 +56,8 @@ The current setup uses these packages and built-in modules: The note system lives under `~/org/` and is organised like this: -- `daily/` for plain daily Org files. +- `journal.org` for the operational work journal. +- `daily/` for older plain daily Org files that may still exist outside the active capture workflow. - `projects/` for project notes. - `areas/` for area notes. - `areas/people/people.org` for the structured people system. @@ -69,8 +70,9 @@ This is a PARA-style layout. Folder placement carries meaning. Denote keywords a The agenda is rule-based. +- The agenda must include `~/org/journal.org`. - The agenda must include recursive scans of `.org` files under `~/org/projects/`, `~/org/areas/`, and `~/org/resources/`. -- The agenda must exclude `~/org/daily/` and `~/org/archives/`. +- The agenda must exclude `~/org/archives/`. - The agenda must use recursive discovery and explicit include and exclude rules rather than heuristic selection. ### Completion setup @@ -152,21 +154,20 @@ from the repo root: The configuration may open the MOC automatically on startup, and `C-c n M` opens it manually. The configuration must not create or manage the file. -Its Quick Access section provides actionable links for opening the agenda, today's note, capture, and a new note, while the rest of the file stays lightweight and curated around active projects, areas, and a few high-leverage resources. +Its Quick Access section provides actionable links for opening the agenda, the journal, capture, and a new note, while the rest of the file stays lightweight and curated around active projects, areas, and a few high-leverage resources. ### Capture Model The capture model has two distinct modes. -### Daily notes +### Journal -Daily notes are plain Org files in `~/org/daily/`, named by date. The workflow expects these headings: +The operational journal lives in `~/org/journal.org`. -- `Tasks` -- `Notes` -- `Open Loops` - -Daily notes are a work journal. They use light structure and are optimised for speed. +- Journal capture uses an Org datetree. +- Each day keeps explicit `Tasks`, `Notes`, and `Meetings` headings beneath the date entry. +- Journal capture is the fast path for operational work. +- The configuration assumes `~/org/journal.org` already exists and does not create it. ### Durable notes @@ -186,12 +187,12 @@ Agenda file selection follows the canonical rules in the `Agenda Rules` section `C-c c` opens capture. The configured templates cover: -- daily tasks -- daily notes -- daily meetings +- journal tasks +- journal notes +- journal meetings - Denote-backed captures for generic notes, projects, areas, and resources -Daily task capture writes under `Tasks`. Daily note capture and daily meeting capture both write under `Notes`, and the meeting template prefixes the heading with a timestamp and the word `meeting`. +Journal task capture writes under the current day's `Tasks` heading. Journal note capture writes under `Notes`. Journal meeting capture writes under `Meetings`, and the meeting template prefixes the heading with a timestamp and the word `meeting`. Denote captures still prompt for title, keywords, and subdirectory placement where appropriate, but folder placement does most of the classification work. The project capture template prepopulates the `project` keyword. Area and resource captures do not inject structural keywords automatically, and there is no Denote-backed meeting capture template. @@ -209,7 +210,7 @@ Denote handles long-lived notes. The main bindings are: - `C-c n i` to insert a canonical person name. - `C-c n I` to insert a compact person summary. - `C-c n L` to show people grouped by location. -- `C-c n d` to open today's daily note. +- `C-c n d` to open `~/org/journal.org`. - `C-c n o` to restore the people overview. - `C-c n O` to show people grouped by role. - `C-c n p` to open `~/org/areas/people/people.org`. @@ -218,6 +219,11 @@ Denote handles long-lived notes. The main bindings are: Keyword prompts and directory placement are part of the workflow, not an afterthought. The config is set up so structure is created first, then capture writes into it, with folder placement carrying most of the durable type information. +The intended split is explicit: + +- `~/org/journal.org` is for fast operational capture. +- Denote notes in the PARA directories are for durable content. + ### Automatic note commits The configuration provides `git-auto-commit-mode` capability. Behaviour is defined in `~/org/.dir-locals.el`. |