building digital garden around zettelkasten
Table of Contents
Originally, zettelkasten includes only ideas that are rather scoped, or timeless, in that it focuses on ideas and universal konwledge, rather than a specific build/implementation project(how a feature of my software “dedicated session” works).
This leaves zettelkasten a solid, well-defined system of notes, while cutting out some expressiveness: you can’t have your journal, diary, project information/proposition or long-term reference like reading list of the year in it, causing the violation of one global entrance
To avoid having to have 2 or more places to store note, one could attach information not legally zettelkasten notes as extension to their zettelkasten.
Ways to extend zettelkasten with some decency
we don’t want to mess our zettelkasten up; you want every merit of a working, well-defined zettelkasten that operates on ideas and knowledge, while being able to dump your projects, reading list and cheatsheets in.
To do that, we need some way of telling your zettelkasten note(zettels) and non-zettelkasten notes apart.
navigation note
put link to all non-zettelkasten notes in a special navigation note called “non-zettel notes” or more specifically “reading list”
* reading list ** sci-fi + roam:sci-fi reading list of 2023 + roam:sci-fi reading list of 2024
namespace in note title
instead of putting note with title project to record how the project feature in your software herman's reactive schedule for human beings, put hrsfhb:project instead, to signify that it is local to the scope of “hrsfhb” (acronym for herman’s reactive schedule for human beings.)
This is similar to how org-roam’s default display template when you have node inside node(displayed as “parent node > children node” in search). But that (node in node) is a terrible idea.
tag
put nz (non-zettelkasten) tag to each note that is non-zettelkasten note, or specific type like (reading list). But tag can be cumbersome to work with