Bible Study: How Joschua uses the LYT frameworks (Obsidian)
Based on Linking Your Thinking with Nick Milo's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use a “garden” staging model (seedling, budding, evergreen) to track which notes need development versus maintenance.
Briefing
A personal knowledge system built in Obsidian is being used to keep Bible study from turning into scattered reading—by turning scripture into a connected, searchable network of notes, verses, and reflections. The core move is treating ideas like a “garden”: notes are “seedlings” to be started, “budding” to be developed, and “evergreen” to be maintained, with saved searches and an “unlinked files” plugin used to recover material that would otherwise get lost as the library grows.
Instead of relying on heavy tagging, the system leans on linking and structure. A “top of mind” area provides quick paths to the notes most likely to be useful, reducing overwhelm when there are many possible directions. For the Bible itself, the workflow centers on building a set of overview notes and “MOCs” (maps of content) that let someone jump into any book of the Bible, then move back to the relevant overview without losing context. From there, specific verses and themes connect outward to other notes—sermons, teachings, personal applications, and book excerpts—so the collection grows “organically” as new insights get attached to the text.
The transcript shows how verse-level linking works in practice. When reading a passage such as Genesis, the interface uses backlinks to reveal where specific verses have been referenced elsewhere in the system. A creation narrative note, for example, includes a link to jump into the start of the relevant section, plus additional links to other notes that cite particular verses (including verse aliases). This makes it possible to move in both directions: from scripture to notes that interpret or apply it, and from a theme note back to the exact biblical location that anchors it.
Beyond scripture, the same connected approach is applied to life and work. Personal growth and mission are organized through MOCs tied to themes like health/body, productivity, and the meaning of work—explicitly connected to biblical passages about labor, identity, and temptation. Inputs are treated as “input” (often books) and outputs as “output” (writings shared with the world), with the system designed to support a practical, scripture-centered way of thinking about society, politics, and everyday decisions.
Book processing is handled with lightweight structure: book notes include metadata such as author, year published, and when it was read, and reading can proceed in stages—outline first (sometimes using highlights), then convert relevant material into new notes while discarding what doesn’t fit. Templates standardize book notes so new entries start consistent. For non-reading tasks, the system also includes “recipes” stored in Obsidian, browsable by ingredient or by recipe, with backlinks that show which recipes use a given ingredient.
Finally, daily journaling is rolled up into weekly and monthly notes, with monthly lookbacks summarizing key events, health status, reading, and gatherings. The overall takeaway is a practical method for managing large bodies of material: keep scripture central, connect notes through backlinks and MOCs rather than sprawling tags, and use garden-style stages plus unlinked-file detection to maintain a living system rather than a static archive.
Cornell Notes
The system uses Obsidian to manage Bible study and other inputs by turning notes into a connected “garden.” Scripture is organized through MOCs and book overviews so readers can jump into any book, then return to the relevant overview while keeping context. Verse-level backlinks make it possible to move from a passage (e.g., Genesis) to every note that cites or applies specific verses, and also trace themes back to the exact text. Instead of heavy tagging, the workflow relies on linking, saved searches, and an “unlinked files” plugin to prevent notes from becoming unreachable. The same connected approach extends to book processing, recipes, and journaling rollups into weekly and monthly summaries.
How does the “garden” metaphor translate into actual organization inside Obsidian?
What makes verse-level navigation work when studying a book like Genesis?
Why use MOCs and book overviews instead of relying mainly on tags?
How does the system handle inputs and outputs differently?
What does book processing look like from raw reading to reusable notes?
How are non-scripture materials integrated without breaking the system’s logic?
Review Questions
- When ideas are categorized as seedling, budding, and evergreen, what mechanisms ensure older notes don’t become unreachable as the library grows?
- How do backlinks enable two-way navigation between a specific Bible passage and the notes that interpret or apply it?
- What staged workflow turns book reading into structured, linkable notes, and how do templates support consistency?
Key Points
- 1
Use a “garden” staging model (seedling, budding, evergreen) to track which notes need development versus maintenance.
- 2
Build Bible navigation around MOCs and book overviews so scripture stays central and context is preserved.
- 3
Rely on backlinks for verse-level navigation, enabling quick movement from a passage to all related notes and back.
- 4
Prevent note rot by using saved searches for key node types and an “unlinked files” plugin to recover disconnected material.
- 5
Process books in stages—outline, then extract only what’s relevant into new notes—while storing metadata for later rollups.
- 6
Standardize recurring note types with templates (especially for books) so new entries are consistent and easier to link.
- 7
Extend the same linking logic to practical domains like recipes and journaling rollups into weekly and monthly summaries.