Get AI summaries of any video or article — Sign up free
Journaling - Managing multiple journals thumbnail

Journaling - Managing multiple journals

6 min read

Based on Obsidian Community Talks's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.

TL;DR

Use a dedicated folder structure for each journaling type (Journal, Dream journal, Workout log, Conditions log, Code diary, Residence calendar, Update log) to keep entries consistent and easy to navigate.

Briefing

A journaling workflow built inside Obsidian is designed to make daily capture feel effortless—so entries actually get written and later reused—by combining a strict folder structure, consistent page templates, and automation via Quick Add. The setup is packaged as a downloadable “showcase vault,” letting others browse the exact formatting rules and copy the system instead of starting from scratch.

At the core is a vault organized around distinct journal types: a Journal folder for day-to-day events, a Dream journal for overnight dreams, a Workout log for exercises, a Conditions log for symptoms, a Code diary for coding notes, a Residence calendar for media that sparks ideas, and an Update log for project changes. Each category has its own page layout, but the naming and metadata conventions stay consistent so searching remains fast. A “Zero dojo” area holds home pages that act like navigation dashboards—month views and lists that point to the underlying entries.

The Journal section uses year-level tracking plus daily pages when something is worth recording. The home view lists months using the tracker plugin and embeds a “2021” year file that aggregates themes and reflections, then links out to the individual entries that occurred in that year. Daily journal pages are kept lightweight: a metadata block appears at the top, followed by headings for events and bullet lists. Some days stay short (a few bullets covering the day’s key moments), while larger days get more detailed event headings so the page remains navigable without splitting into multiple notes.

A major usability choice is file naming. Journal entries start with the date, then a dash, then a category marker—“j” for journal entries—followed by a short title. That makes search trivial: typing “j” surfaces all journal entries, while the title itself (often 3–4 words) summarizes what happened without forcing a click-through. Related events are grouped using symbols in the title (like “&” and “+”), so the filename communicates relationships at a glance.

Dream journal pages follow the same metadata approach but use free-form paragraph writing, with tags describing dream content and optional internal sections for long dreams. Workout logs use template variants keyed to body-part focus (for example, leg day vs torso day vs arms), and include structured tables for exercises, reps, rest, and notes on pain or difficulty. Conditions log entries capture symptoms with fields for severity, possible cause, body area, and a concise event summary—useful later when recalling details for a doctor.

The system also supports “resonance” notes tied to media. Those pages embed the video when possible (or link to the source), store creator/title metadata, and include a “progress” tag during active note-taking to reduce visual clutter and encourage completion. For coding and project work, the Code diary breaks down snippets (including regex and JavaScript examples) so the “how” and “why” remain recoverable later, while the Update log tracks changes to projects like themes with dated bullet lists.

Automation ties it together: Quick Add is mapped to Alt J and generates new entries from templates, placing them into the correct date folder and applying the right filename prefix and structure. The creator reports that setting up the Quick Add templates took about 30 minutes once the system existed, and the habit-building routine is simple—open Obsidian immediately after waking to capture dreams—so the workflow reduces friction enough to stick.

Cornell Notes

The journaling system uses Obsidian to reduce friction: strict folders, consistent templates, and automation so daily capture happens quickly and stays searchable. Entries are organized by type—Journal, Dream journal, Workout log, Conditions log, Code diary, Residence calendar, and Update log—while navigation “home pages” provide month and year overviews. File titles follow a predictable pattern (date + category marker like “j” for journal entries), making search fast and letting filenames summarize what happened. Quick Add (Alt J) generates new notes with the correct template and date placement, so users don’t have to build structure manually. The result is a workflow that supports both quick daily logging and later retrieval of details.

How does the setup keep journaling searchable without relying on complex queries?

It standardizes file titles and metadata. Journal entries begin with the date, then a dash, then a category marker—“j” for journal entries—followed by a short title (often 3–4 words). That means searching for “j” returns all journal entries immediately. The title itself also summarizes the day’s key events so a user can often identify content without opening the note. Related events are grouped using symbols in the title (like “&” and “+”), so filenames communicate connections at a glance.

What’s the difference between the Journal, Dream journal, and Conditions log page styles?

Journal pages are event-oriented bullet lists under headings, with a metadata block at the top; days can be short or expanded with more event headings when needed. Dream journal pages keep the same metadata structure but use free-form paragraph writing to record dreams, with tags describing dream themes and optional internal sections for long dreams. Conditions log entries focus on structured recall: fields capture distress/pain level, possible cause, body area, and symptom details, plus an event summary describing what happened when the symptom occurred.

How does the Workout log handle different training days without creating a messy notebook?

It uses template variants keyed to body-part focus. The file title includes an extra initial to indicate leg day vs torso day vs arms day (for example, “l” for leg day). Each variant links to a table of exercises and records time, reps, rest, and notes about pain or difficulty. There’s also a general “w” template for ad-hoc workouts like a few push-ups or squats, keeping structure consistent even when routines vary.

What role do “resonance calendar” notes play, and how are they written during active viewing?

Resonance calendar notes capture media that sparks ideas or challenges thinking. Each note stores creator and title metadata and embeds the media when possible (otherwise it keeps a source link). Notes are written alongside the media; when the note is still being built, a “progress” tag is placed at the top to make the unfinished state visually obvious and motivate completion. The creator also uses split-view so the video can keep playing while notes are added.

How does Quick Add (Alt J) reduce the effort of creating new entries?

Quick Add is mapped to Alt J and generates new notes from templates. It prompts for key inputs like the entry title, then automatically applies the correct date folder placement and filename formatting (including category prefixes such as “j” for journal entries). For more complex logs like workouts, it can also use multiple selects (e.g., arms/torso/leg or meeting/project types) so the right template structure appears immediately, avoiding manual setup.

Why does the system prefer one journal entry per day instead of splitting into week/month notes?

The creator says week/month entries felt too narrow and added upkeep. Instead, the system uses a year entry plus daily entries only when something is worth recording. When a day becomes large, the note grows via headings and sub-bullets rather than creating a new page, which keeps linking simple—specific events can be referenced by heading within the same daily note.

Review Questions

  1. What filename conventions in this system make it easy to find all entries of a certain type (e.g., journal entries) quickly?
  2. How do template variants in the Workout log change the structure of the note depending on training focus?
  3. What automation does Quick Add perform beyond simply creating a blank note (e.g., folder placement, prefixes, and template selection)?

Key Points

  1. 1

    Use a dedicated folder structure for each journaling type (Journal, Dream journal, Workout log, Conditions log, Code diary, Residence calendar, Update log) to keep entries consistent and easy to navigate.

  2. 2

    Adopt predictable file naming: date + category marker (like “j” for journal entries) + short event title so search works instantly.

  3. 3

    Keep daily journal pages navigable by using headings and bullet lists; expand with subheadings when a day grows rather than splitting into many notes.

  4. 4

    Use template variants for structured logs (workouts and conditions) so the same fields appear every time and later recall is faster.

  5. 5

    Store media-based insights in resonance notes with embedded playback when possible, and use a visible “progress” tag during active note-taking.

  6. 6

    Automate note creation with Quick Add (Alt J) so templates, prefixes, and date folder placement happen automatically.

  7. 7

    Build a habit by capturing immediately after waking (especially dreams), reducing the delay that causes long backlogs.

Highlights

The system’s biggest search advantage comes from file titles that start with the date, include a category marker (like “j”), and use short event summaries—so filenames often answer “what happened?” without opening the note.
Workout logging stays structured despite changing routines by using template variants keyed to body-part focus (e.g., leg day vs torso day) and recording reps/rest/pain in tables.
Resonance calendar notes embed the media and use a “progress” tag during note-taking, turning unfinished work into a visual nudge to finish.

Topics

  • Obsidian Journaling
  • Quick Add Automation
  • Dataview Navigation
  • Template Variants
  • File Naming Conventions

Mentioned

  • Mike Schmitz
  • PKM