Lets Learn Obsidian.md - Installation and First Notes
Based on Josh Plunkett's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Obsidian.md stores campaign notes locally in a “vault,” which is just a folder on the device, reducing dependence on internet access during sessions.
Briefing
Obsidian.md is pitched as a free, markdown-based note system built for tabletop role-playing games—where the standout feature is how effortlessly one note can link to another, turning NPCs, locations, items, and campaign lore into a connected knowledge base. The practical payoff is speed and organization: as notes are written, links form automatically, and the resulting structure can be visualized (via graph view) or navigated through folders and headings.
A key theme is control over data. Notes live locally on a PC or device inside a “vault,” which is essentially a folder Obsidian manages. That local-first approach is contrasted with subscription-based online campaign managers, especially in scenarios where internet access fails at the table. The workflow described is straightforward: download Obsidian for the operating system (Mac, Linux, Windows) and also use it on mobile devices (iOS/Android), then create a new vault by pointing Obsidian to a folder location.
From there, the tutorial demonstrates the basics that make the tool feel powerful even before plugins. Notes are plain text files, typically with a .md extension, meaning they can be opened later in standard editors like Notepad. Formatting relies on markdown conventions: headings use hash marks (#, ##, ###) to create a collapsible hierarchy; bullet points use dashes; bold uses Control+B; italics uses single asterisks. The emphasis is that markdown is easy to learn and future-proof, since the underlying data remains accessible.
The “core feature” is linking. By typing [[ and then selecting or typing a note name, Obsidian creates internal links between notes. Hovering can show previews, and those links then power navigation and visualization. Graph view is introduced as a way to see connections between notes as nodes and edges; it can be fun and useful for understanding a campaign’s structure, though it may slow down if used heavily.
Organization is handled through folders and a recommended attachment strategy. The tutorial shows creating folders for categories like NPCs and locations, then linking notes across that structure (e.g., an NPC working at a blacksmith in a city, which sits inside a region). For images, it recommends a dedicated “Z_” attachments folder and using “Set as attachment folder” so pasted images land in a consistent place. Renaming images can optionally update all references automatically.
Finally, settings are framed as the difference between “just notes” and a tailored RPG workspace. Appearance themes can be swapped, editor options can change readability and line length, and spell check can be enabled with a chosen dictionary (including an Australian English option). Rendering behavior is adjustable through editing/preview modes and “live preview” preferences. The tutorial also points to core and community plugins as the “magic garden” that can transform Obsidian into a full campaign management system—mentioning features like automatic linking, step blocks, initiative trackers, maps with pins, and even AI-assisted generation—while keeping the initial learning curve manageable.
Cornell Notes
Obsidian.md is presented as a free, local-first note system for tabletop RPG campaigns, built around markdown and internal linking. Notes are stored in a “vault,” which is just a folder on a device, so the data stays under the user’s control and remains accessible even without internet. Markdown formatting uses simple syntax like # for headings, dashes for bullet points, Control+B for bold, and single asterisks for italics. The standout capability is linking notes with [[note name]], which creates a web of relationships among NPCs, locations, and items; graph view can visualize those connections. Organization is reinforced with folders and a dedicated attachments folder for images, keeping the vault tidy as content grows.
Why does local storage matter for a tabletop campaign manager, and how does Obsidian handle it?
What makes Obsidian’s notes “future-proof” compared with many online tools?
How do internal links work, and what do they enable for campaign organization?
What is graph view, and when might it be less practical?
How should images be managed so the vault stays organized?
Which settings and markdown features are highlighted as most useful for first-time users?
Review Questions
- How does creating a vault relate to Obsidian’s local-first approach, and what practical risk does that reduce during gameplay?
- Describe the markdown syntax used for headings, bullet points, bold, and italics in this tutorial.
- What steps create an internal link between two notes, and how does graph view use those links to visualize relationships?
Key Points
- 1
Obsidian.md stores campaign notes locally in a “vault,” which is just a folder on the device, reducing dependence on internet access during sessions.
- 2
Internal linking with [[note name]] turns separate notes (NPCs, locations, items) into a connected system that can be navigated and previewed.
- 3
Markdown formatting is intentionally simple: # headings create a hierarchy, dashes create bullet points, Control+B makes bold, and single asterisks make italics.
- 4
A consistent folder structure—such as separate folders for NPCs and locations—helps keep large campaigns searchable and logically organized.
- 5
Images should be managed with a dedicated attachments folder (e.g., Z_attachments) using “Set as attachment folder” so pasted files don’t clutter the vault.
- 6
Editor and appearance settings (themes, readable line length, spell check, live preview behavior) can significantly change day-to-day usability.
- 7
Community and core plugins are positioned as the main path from basic notes to full RPG tooling like trackers, maps, and automation.