Getting Started: Taking Smart Notes in Obsidian

Obsidian is set up as a fully local, Markdown-based note system built around linking ideas rather than sorting them into rigid folders. After installing Obsidian from obsidian.md, the workflow starts with creating a “vault,” which is the local storage location for all notes. Because the files live on the user’s computer as plain Markdown, the knowledge remains under the user’s control even if syncing services change or disappear. That portability also matters: Markdown transfers cleanly into other formats like HTML and can be exported to outputs such as PDF and EPUB, making the notes useful beyond the app itself.

The setup then leans into a key tradeoff: Obsidian’s flexibility can also become a distraction. To keep the system usable, the configuration intentionally avoids community plugins and sticks to the built-in core plugins that support a “smart notes” workflow. The first core feature enabled is Daily Notes. A dedicated “daily notes” folder is created, then the Daily Notes core plugin is toggled on so each day generates a new note named by year-month-day and stored in that folder. This separation is treated as essential for preventing the “insurmountable mess” that happens when fleeting thoughts, literature, and permanent notes all get mixed together in one place.

Next comes the reference system, implemented as a separate “reference” note space for literature notes. The distinction is straightforward: fleeting notes are temporary reminders meant to be deleted once they’ve served their purpose, while literature/reference notes are kept permanently because they capture information worth revisiting. The transcript frames this as a way to avoid clutter and preserve the ability to refresh understanding without rereading entire sources.

For the permanent layer, the system adds a “slip box” using the Zettelkasten Prefixer core plugin. A “slip box” folder is created, then the Zettelkasten Prefixer is enabled so new Zettelkasten notes get automatically generated IDs based on timestamps. The approach is intentionally opinionated: rather than forcing meaningful names at creation time, the plugin handles naming to reduce “availability bias” (only remembering recently created notes) and to avoid the “first time principle” problem where naming becomes the hardest part and slows writing. The configuration also offers options like templates and an ID format, and it can separate the act of writing a note from adding it into the slip box.

Finally, a “projects” folder is introduced as the practical engine for turning notes into output. Project-related notes hold scripts, outlines, and other work artifacts tied to concrete goals—like drafting a book chapter or planning a YouTube video. Fleeting notes can start the chain (e.g., “buy this book” or “read this article”), then evolve into literature/reference notes, and later into project work. The overall point is that the system’s structure—daily notes, reference, slip box, and projects—creates a workflow that supports content creation while limiting the chaos that comes from an overly open-ended tool.