Tour of My Obsidian Vault
Based on Knowledge Work Nexus's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Obsidian’s core advantage is that notes are stored as plain Markdown files, keeping the content readable outside the app.
Briefing
The core takeaway from this Obsidian vault tour is that Obsidian’s value comes from combining highly customizable organization with “future-proof” storage: everything lives in plain Markdown files on your device, while themes, plugins, and views add powerful ways to navigate and visualize that data. The presenter’s vault is used as a concrete example of how different settings—dark vs. light mode, community themes, layout choices, and plugins—can make the same underlying system feel completely personal.
A major early focus is appearance and interface control. The vault is running on a dark theme, and Obsidian supports switching between base light and dark modes. Beyond that, the look can be further shaped by community themes; one favorite mentioned is “Things by Colin Eckert,” which affects not just colors but also how text feels on a page. The tour also notes that themes can be created via CSS, giving users a path to deeper customization without changing the underlying structure.
Organization and navigation are treated as flexible rather than fixed. The left-side file explorer is arranged into a para-style structure—projects, areas, resources, and archives—attributed to Thiago Forte’s methodology. However, the vault isn’t treated as a rigid template; the presenter says parts of that approach are “falling apart” and that tweaking is part of the process. To help users who don’t know where to start, a calendar view is highlighted as a practical alternative to relying on links alone. The calendar plugin makes it easy to see which days have daily notes and even approximate word counts, using a dot-based setting (for example, a dot corresponds to about 250 words, adjustable to match the user’s preferences).
The tour then leans into Obsidian’s distinctive “graph” view. No two users’ graphs look the same because the connections and data patterns differ. The graph is presented as a way to explore notes through serendipity—jumping from one node to another to discover related material, such as book notes.
A key benefit is also framed as resilience and control over data. Obsidian can be used locally and synced with the Sync plugin, with options to publish selected parts to the web via the Publish plugin. The presenter emphasizes that files are stored as normal documents (in the example, stored in OneDrive, though local storage is also possible), meaning the content remains readable even outside Obsidian. A mind map visualization is used to demonstrate this: even if a plugin or visualization layer changes, the underlying Markdown source file remains accessible—shown by opening the file in Notepad.
Finally, the tour points to additional power layers like the Data View plugin, which can query the vault for stats and custom lists. The session ends by teeing up a follow-up video focused on setting up a first Obsidian vault, reinforcing the message that the system is both customizable now and designed to stay usable long-term.
Cornell Notes
Obsidian’s standout strength is that it blends customization with durable storage. Themes (dark/light and community CSS themes like “Things by Colin Eckert”), flexible file explorer structures (including a para-style setup), and plugins (calendar, graph, mind map, data view) change how notes are organized and discovered. The calendar plugin can show which days have daily notes and approximate word counts using configurable dot settings. The graph view is unique to each vault because it reflects how notes are linked. Crucially, the notes themselves are plain Markdown files stored locally and can be synced or published, so the content remains readable even if a plugin or Obsidian setup changes.
Why does the tour repeatedly emphasize that Obsidian data is “future-proof”?
How do themes change the day-to-day experience of using a vault?
What practical problem does the calendar plugin solve for daily notes?
What makes the graph view different from user to user?
How does Obsidian balance local control with syncing and publishing?
What role does Data View play in turning notes into a queryable system?
Review Questions
- What evidence in the tour shows that Obsidian content remains accessible even if a plugin or visualization layer changes?
- How do the calendar plugin’s dot settings help estimate daily note volume, and why might that matter for planning?
- What factors cause two Obsidian graph views to look different, and how can that difference support note discovery?
Key Points
- 1
Obsidian’s core advantage is that notes are stored as plain Markdown files, keeping the content readable outside the app.
- 2
Dark/light base themes can be switched easily, and community themes (like “Things by Colin Eckert”) can reshape typography and page styling.
- 3
A vault’s structure is customizable; even a para-style file explorer (projects, areas, resources, archives) can be adjusted when it stops fitting.
- 4
The calendar plugin provides a fast daily-notes overview, including configurable dot-based word-count estimates.
- 5
The graph view is unique to each vault because it mirrors the specific linking and data patterns in that collection.
- 6
Obsidian supports local-first use with optional Sync for mobile and Publish for sharing selected content on the web.
- 7
Plugins like mind map and Data View add powerful visualizations and queries without changing the underlying text files.