Get AI summaries of any video or article — Sign up free
Do You Have a Dashboard for Your Thoughts? (Obsidian Tutorial) thumbnail

Do You Have a Dashboard for Your Thoughts? (Obsidian Tutorial)

5 min read

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.

TL;DR

Ace organizes Obsidian work into Atlas (knowledge), Calendar (time), and Efforts (actions) to keep attention aligned with what’s needed now.

Briefing

A unified Obsidian system built around links—rather than folders—aims to keep ideas flowing from capture to connection to communication, so knowledge doesn’t get “squished” by over-collecting. The core promise is “Ace,” an Atlas Calendar Efforts framework that organizes attention across three dimensions: where ideas live (Atlas), when they matter (Calendar), and what they turn into (Efforts). The practical payoff is speed and creativity: new notes (“sparks”) are automatically routed into a single intake area, then moved into the right knowledge context through lightweight commands and link-based relationships.

The tutorial starts by contrasting traditional folder workflows with a link-first approach that better matches how the brain naturally associates concepts. Instead of treating notes as static files, it treats them as living pieces that can be connected, revisited, and developed. The “ideaverse” home note becomes the launch pad: it surfaces Atlas calendar and efforts, plus links that let users jump into the right mode instantly—knowledge work, time-based journaling, or action management.

Atlas is presented as the knowledge layer, where “add” becomes “relate” and then “communicate.” The workflow begins with capturing: pressing Command N (or Ctrl N on Windows) creates a new note (“new spark”) that lands in an “add” area organized by how long notes have been alive. From there, a quick command (Command M / Ctrl M) moves the note into the Atlas structure—such as placing it under “ideas”—so it stops being just a scratchpad and becomes part of a growing network.

Relating is where folders are intentionally minimized. The system leans on links to build sideways relationships rather than hierarchical trees. A “related” view is powered by the Excalibrain plugin, which displays a map-like relationship layout so users can see connections without forcing a top-down taxonomy. Save searches with tags (for example, tags tied to “note boat” or “note develop”) help “future you” resume work on ideas that need development, turning passive storage into an active pipeline.

Communication is framed as the point where ideas become usable output—tracked communications, reports, or other deliverables—supported by the related network. The tutorial then widens Atlas with optional maps: a Library for knowledge management classification (based on existing systems like Cutter, Dewey, and Universal Decimal Classification, but simplified to avoid brittle number-heavy schemes), a People map that tags individuals with dates and enables sorting by shared birth timing, and a Sources map for managing reading materials. Sources are treated as raw inputs that can be clipped elsewhere (read-it-later or “anti-library” approaches), then imported into the ideaverse as separate notes so they can be connected to other ideas and turned into original insights.

Finally, Calendar handles time-based work: daily notes for quick capture, logs for structured idea capture (like an “idea log” with links to internal notes and external URLs), and a broader “time travel” concept that supports planning, reflection, and synthesis. The tutorial closes by previewing Efforts—action management—promising a follow-up on GTD-style projects and a “four intensities of efforts” approach for both clear and fuzzy tasks.

Cornell Notes

Ace organizes Obsidian work into three linked layers: Atlas (knowledge), Calendar (time), and Efforts (actions). Notes start as “sparks” captured quickly into an “add” area, then get moved into Atlas contexts (e.g., ideas) using fast commands. Instead of relying on folders for structure, the system emphasizes links and a “related” map view (via the Excalibrain plugin) to build sideways relationships and help future-you resume development. Atlas can also include optional maps like Library (classification), People (tagging with dates), and Sources (reading inputs turned into connected insights). Calendar then supports daily capture, logs, planning, reflection, and synthesis—so ideas don’t just accumulate; they get communicated and acted on.

How does Ace move a note from “captured” to “useful” without folder-heavy organization?

Capture creates a new “spark” (Command N / Ctrl N) that automatically lands in a single “add” area. A second command (Command M / Ctrl M) moves that note into the Atlas structure—such as placing it under “ideas.” From there, “relate” uses links to connect the new note to known concepts, and “communicate” turns those connections into output (tracked communications, reports, or deliverables). The key shift is treating notes as living objects that can be revisited and linked, not just filed.

Why does the tutorial push links over folders during the “relate” stage?

Folders can help sometimes, but they also get in the way of creative association. The system closes folders to reduce friction and relies on links to create sideways relationships rather than hierarchical trees. The “related” view reinforces this by showing connections in a map-like layout, so users can navigate the ideaverse quickly and see how ideas connect without forcing them into a rigid taxonomy.

What role does Excalibrain play in the workflow?

Excalibrain is used to generate a “related” map view inside the note properties area. In that view, relationships appear as non-hierarchical connections: “up” corresponds to the home note, while “sideways” relationships show linked notes rather than a parent-child folder structure. This helps users fly around their ideaverse and spot connections that might otherwise stay buried.

How does Ace handle sources like books and articles without turning the system into a cluttered archive?

It recommends separating raw intake from active development. Clipping can happen in a read-it-later app or an “anti-library,” then later imported into the ideaverse as a dedicated note when the material is ready to be worked on. Once in Atlas under “sources,” those inputs can be linked to other notes and ideas, turning dead-tree reading into living, communicable insight.

What does Calendar add beyond simple journaling?

Calendar supports multiple time-based modes: daily notes for fast capture (Command D / Ctrl D), logs for structured entries (like an “idea log” with links to internal notes and external URLs), and zoomed-out planning and reflection. The tutorial frames this as “time travel”: retrieving old notes by time, emotionally revisiting past context, and synthesizing earlier thoughts into consolidated wisdom notes.

How does the People map generate new insights?

People notes tag individuals and include dates (such as birth dates). Sorting by those dates can surface unexpected overlaps—for example, identifying two admired people born on the same day. The tutorial uses that kind of pattern discovery to spark new ideas (including a “five decade rule”), illustrating how linking and sorting can produce fresh perspectives.

Review Questions

  1. What specific commands are used to create a new spark and then move it into the Atlas structure, and what does each step accomplish?
  2. How does the “related” view differ from folder hierarchies, and what does that enable during idea development?
  3. What are the distinct purposes of Atlas, Calendar, and Efforts in the Ace system, and how does each one support a different stage of turning thoughts into output?

Key Points

  1. 1

    Ace organizes Obsidian work into Atlas (knowledge), Calendar (time), and Efforts (actions) to keep attention aligned with what’s needed now.

  2. 2

    New notes (“sparks”) are captured quickly into a unified “add” area, then moved into Atlas contexts using fast commands (Command N / Ctrl N, then Command M / Ctrl M).

  3. 3

    Relating ideas relies on links and sideways relationships rather than folder hierarchies, reducing friction during creative association.

  4. 4

    The Excalibrain plugin provides a map-like “related” view that helps users navigate connections without forcing a top-down structure.

  5. 5

    Atlas can be extended with optional maps such as Library (simplified classification), People (tagging with dates), and Sources (turning reading inputs into connected insights).

  6. 6

    Sources intake is separated from active development: clip elsewhere first, then import into the ideaverse when ready to connect and cultivate ideas.

  7. 7

    Calendar supports daily capture, structured logs, planning, reflection, and synthesis—so ideas can be retrieved by time and transformed into consolidated wisdom.

Highlights

Ace treats notes as living things: capture (“add”) leads to connection (“relate”) and then to output (“communicate”).
Folders are intentionally minimized during relating so links can create sideways, non-hierarchical relationships.
Excalibrain’s related map view turns linked notes into a navigable relationship layout inside note properties.
Sources work best when raw intake is separated from active development, then imported into Atlas for connection and insight-building.
Calendar enables “time travel” through daily notes, logs, planning, reflection, and synthesis into new wisdom notes.

Topics

  • Ace Framework
  • Obsidian Links
  • Atlas Knowledge
  • Calendar Time Travel
  • Efforts Actions