Get AI summaries of any video or article — Sign up free
How I Easily Brainstorm 🧠 and Write 📝 using Obsidian MD thumbnail

How I Easily Brainstorm 🧠 and Write 📝 using Obsidian MD

John Mavrick Ch.·
5 min read

Based on John Mavrick Ch.'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 Dataview index note to list newsletter editions sorted by publish date, pulling from a dedicated output folder.

Briefing

Writing doesn’t have to begin on a blank page when a note system turns past ideas into ready-to-use building blocks. The workflow described here centers on Obsidian as an “information bank,” where newsletter drafts are assembled by linking inputs (highlights, reflections, and daily notes) to a reusable template, then pulling the most relevant pieces into a cohesive weekly post. The payoff is an incremental writing process: consume, capture, connect, outline—then publish—without starting over from scratch each time.

At the core is a newsletter workspace anchored by a main index note that lists every edition using Dataview queries. Those queries pull notes from a dedicated newsletter folder and sort them by publish date, making it easy to track output over time. Each new edition is generated from a template using Templater variables that automatically set headers and the newsletter structure. The newsletter content itself is built from a consistent set of categories: what was interesting from the week, personal experiences and reflections, insights from content consumed, and “ramblings” gathered from walks or self-examination.

The vault’s note types function like modular ingredients. Input notes store highlights and thoughts from things consumed, along with started/finished dates to preserve context and enable later linking. Thought notes capture more personal, subjective ideas—kept distinct from objective notes—so the draft can mix insight with lived experience. For quick capture while away from a desktop, Fleeting notes are handled through an app called Fleeting Notes, which syncs with Obsidian and supports linked ideas; it’s used for notes from YouTube videos, walks, and spontaneous thoughts. Daily notes then provide the raw material for consistency and authenticity: small snippets that may not matter alone become meaningful when reviewed together during a weekly cycle.

When drafting, the process starts with automation and retrieval. A command palette shortcut creates a new newsletter note and assigns the next edition number, leaving it ready for filling in. The writer then scans daily notes and weekly review artifacts to extract accomplishments, categorize life updates, and identify resources worth sharing. Concrete examples of linked themes are pulled from multiple sources—such as Jeff Bezos’s remarks about conformity, the “purple cow” concept about standing out, and a personal discovery that ties entertainment and attention—so the final newsletter section can unify them under a shared idea: uniqueness versus conformity.

To keep the writing relevant even when older ideas are needed, the workflow leans on search and backlinks. Quick Switcher searches surface notes tied to “writing” and “note storage systems,” which then connect to concepts like the Zettelkasten “slip box” method (via “zettelcost”/“zelicostin” references), evergreen notes, and the role of connections in retrieving and recombining knowledge. Backlinks help the writer jump from a concept note to related resources, including guidance on turning notes into articles and books using Obsidian.

Once the draft is assembled, the final step is publishing to Substack, then converting the published text into new Obsidian notes. Those new notes are linked back into the vault—turning the newsletter into future input. The result is a system where writing becomes a loop: capture ideas, connect them to existing structures, draft faster, publish, and then feed the output back into the knowledge network.

Cornell Notes

The workflow uses Obsidian as an “information bank” so writing becomes an assembly process rather than a blank-page task. A Dataview-powered index tracks newsletter editions by publish date, while Templater generates new edition notes with consistent headers and structure. Inputs come from multiple note types—input notes for highlights, thought notes for personal ideas, Fleeting Notes for quick capture on the go, and daily notes for weekly review. Drafting then relies on scanning daily and input notes, embedding or copying relevant snippets, and using backlinks/Quick Switcher to retrieve older ideas tied to writing and note-storage methods like Zettelkasten. Publishing to Substack is followed by converting the output into new linked notes, strengthening the vault for future writing.

How does the system make it easy to start a new newsletter edition without manual setup?

A command palette shortcut creates a new note automatically. The template uses Templater variables to fill in the newsletter structure and set the title, while the edition number is inserted during creation (e.g., “11th edition”). The new note appears in the newsletter list; if it has no publish date yet, it lands at the bottom of the Dataview-sorted index.

What role do Dataview queries play in keeping newsletter work organized over time?

Dataview queries power a main index note that pulls all newsletter edition notes from a specific folder (the output/newsletter folder). The query sorts results by publish date, so past editions are searchable and ordered chronologically, which supports both drafting and reviewing.

Why split notes into input notes, thought notes, fleeting notes, and daily notes?

Each note type serves a different function in the writing pipeline. Input notes store highlights and thoughts from consumed content and include started/finished dates for context. Thought notes capture more personal, subjective ideas distinct from objective material. Fleeting Notes handles quick capture away from a desktop and syncs with Obsidian while supporting links. Daily notes support consistency by collecting small day-based snippets that become useful when reviewed together during a weekly cycle.

How does the workflow turn scattered weekly material into a unified theme for the newsletter?

During drafting, the writer scans daily notes and content logs to find candidate snippets, then embeds or copies them into the draft. Multiple sources are grouped under a shared idea—for instance, Jeff Bezos’s conformity framing, the “purple cow” uniqueness example, and a personal discovery are all connected to the theme of standing out versus blending in.

How does the system retrieve older, “hidden” ideas when the current week isn’t enough?

Quick Switcher search and backlinks are used to locate concept notes tied to writing and note-storage systems. Searching for “writing” surfaces notes about note storage and linked thinking, which connect to a slip box/Zettelkasten-style approach (referred to as “zettelcost”/“zelicostin”), evergreen notes, and connection-focused retrieval. Backlinks then reveal related notes to expand the draft’s structure.

What happens after publishing, and why does that matter for long-term writing speed?

After finishing the draft, the writer publishes to Substack, then converts the text blocks into new Obsidian notes. Those new notes are linked to existing concepts (e.g., uniqueness/authenticity/productivity themes) so the next writing cycle starts with stronger connections and more reusable material already in the vault.

Review Questions

  1. Describe how Dataview and Templater work together in this workflow to manage newsletter editions from creation to organization.
  2. What specific note types feed the newsletter, and what does each one contribute during drafting?
  3. How do backlinks and Quick Switcher searches help the writer reuse older ideas when building new drafts?

Key Points

  1. 1

    Use a Dataview index note to list newsletter editions sorted by publish date, pulling from a dedicated output folder.

  2. 2

    Generate each new newsletter edition from a Templater-based template so headers and structure are consistent every week.

  3. 3

    Feed the drafting process with multiple note types: input notes (highlights), thought notes (personal ideas), Fleeting Notes (quick capture), and daily notes (weekly review material).

  4. 4

    Draft by scanning daily and input notes, then embed or copy relevant snippets into the template and group them under a shared theme.

  5. 5

    Rely on Quick Switcher and backlinks to retrieve older concepts and expand outlines using linked-thinking methods like Zettelkasten/slip box and evergreen notes.

  6. 6

    After publishing to Substack, convert the published content back into linked Obsidian notes so future drafts start from accumulated connections.

Highlights

A single command palette action creates a new newsletter note with the correct structure, turning weekly publishing into a repeatable routine.
The newsletter theme is built by linking multiple sources—such as Jeff Bezos’s conformity idea and the “purple cow” uniqueness concept—into one cohesive section.
Backlinks and concept searches let older “writing system” notes (slip box/Zettelkasten, evergreen notes, connections) directly inform new drafts.
Publishing isn’t the end: the workflow turns Substack output back into Obsidian notes, strengthening the vault for the next cycle.