Build projects from Smart Notes in Obsidian

The core move is turning “Smart Notes” into a practical Obsidian workflow by using a dedicated project outline inside Obsidian—then keeping reference and long-term knowledge separate from the actual writing. The approach matters because it prevents the system from becoming cluttered: notes collected for learning and synthesis stay organized, while writing stays focused and manageable.

The workflow starts from Graph View and uses a “project note” as the entry point. A folder named “projects” becomes the container for project-specific material, including a traditional header-based outline written in Markdown. In this structure, headings map directly to hierarchy: “##” functions as an H2, “###” as an H3, and so on. The outline includes sections such as an introduction and a “configure environment” area that reflects the course’s guiding principle—simplicity prevents complexity, and exceptional results come from a simple system. The emphasis is deliberate: the setup avoids heavy plugin use and fancy markup so the system doesn’t distract from the underlying method.

Within the outline, the workflow translates Smart Notes concepts into Obsidian components. “Fleeting” notes become daily notes, while “reference” and the “slip box” are treated as folders. The example shows a progression through the system: capture fleeting notes, organize them under the right headings, and then accumulate permanent notes that can later feed writing. The project outline is used as an organizing scaffold—essentially an outline for drafting—while the slip box remains a separate long-term knowledge store.

A key practical detail is how the notes are used while writing. The creator describes working with two screens (or macOS workspaces) so that the writing tool stays open while Obsidian’s project outline is visible for quick reference. Ulysses is used as the editor for drafting, with Obsidian serving as the reference system and slip box. This separation is presented as a quality-of-life improvement: Ulysses exports to PDF and other book formats more smoothly, while Obsidian remains optimized for Markdown-based note management.

The transcript also addresses a common failure mode: taking too many notes. The example graph suggests only a subset of captured notes were actually used—around 30—implying that earlier note-taking produced more quantity than needed. The guidance is to expect that: quantity comes before quality. If a vault needs restarting, that’s framed as normal—using a “scorched earth” approach to begin fresh, carry forward only the lessons (and later, only a subset of notes), and avoid dragging forward everything from earlier experiments. Over time, the notes become shorter and more selective, improving their usefulness for writing.

In short, Smart Notes become a writing engine when Obsidian is structured into reference and slip-box folders, while project notes act as the drafting outline—and writing happens in a dedicated editor like Ulysses to keep the workflow clean and export-friendly.