The Complete Obsidian Second Brain Tutorial for Beginners
Based on Systematic Mastery's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Use PARA-style folders—Areas, Projects, Resources—to separate ongoing themes, time-bound goals, and reusable/reference material.
Briefing
A beginner-friendly Obsidian “second brain” setup gets built from scratch around a simple folder system—Areas, Projects, Resources—then gets reinforced with a carefully chosen set of plugins and defaults. The core idea is to keep a small, stable set of recurring life topics (Areas), track time-bound goals and deliverables (Projects), and store reusable or reference material (Resources) so notes don’t get stranded when projects get archived.
The walkthrough starts by creating a new vault (“walkthrough”) and immediately establishing the PARA-inspired structure. “Areas” becomes the home for ongoing themes people return to—examples include exercise, personal growth, and an inbox. “Projects” holds work with a due date and a clear outcome, such as “devops improvements” or “read this book and process all the notes.” “Resources” is intentionally looser: it can include notes on books, people, and meetings, but it’s meant for material that shouldn’t disappear just because a specific project folder gets archived. A key operational detail is the “inbox” area: new notes land there first, then get sorted during a weekly review so they don’t accumulate in the wrong place.
To make this structure usable day-to-day, the setup introduces “domain routes,” a routing layer that links notes to a domain-specific path. Domains represent recurring interests where people spend time and take notes—programming, economics, cryptocurrency, physical fitness, psychology, data science, and more. The graph view is positioned as a way to see where attention and note-taking have concentrated, and where knowledge gaps may exist. Domain routes also support a practical workflow: programming-related notes live under the programming domain, and opening the graph for that domain surfaces related work.
After the folder architecture, the tutorial shifts to configuration and plugin selection. It turns off readable line length for full-width notes, enables folding headings and indents, sets new-note location to the inbox, and chooses shortest-path wikilinks. Appearance is set to dark mode with a minimal theme and larger font size. On the plugin side, it installs tools for navigation and organization (Quick Switcher, Graph View, Backlinks, Tag Pane), layout and editing (Sliding Panes, Outliner, Syntax Highlighting), and productivity scaffolding (Advanced Tables, Kanban, Periodic Notes, Templater, Workbench, periodic/daily templates). It also enables Obsidian Sync concepts for cross-device access and mentions encryption options for sensitive vault content.
The build culminates in configuring templates and plugin behavior: Kanban uses a “kanban tasks” folder and a main note template that links to the daily note by date. Templater is set to trigger on new file completion, Workbench is configured as a running collection of active notes, and Zettelkasten-style creation is set up to automatically prefix new notes with dates for timeline clarity and sorting. Finally, a new note is created using a shortcut, with follow-up videos promised for deeper dives—especially Kanban, Periodic Notes, and Templater.
Cornell Notes
The setup builds an Obsidian “second brain” from scratch using a PARA-style structure: Areas for ongoing life topics, Projects for time-bound goals, and Resources for reusable/reference material that shouldn’t vanish when projects are archived. A dedicated inbox becomes the landing zone for new notes, then gets processed during weekly review so notes end up in the right place. To connect notes to recurring interests, it adds “domain routes” that organize content by domains and uses graph view to reveal where effort and learning have concentrated. The workflow is powered by a curated plugin stack—Kanban for tasks, Periodic Notes for dated daily pages, Templater for template automation, and Workbench for a “currently active” note collection—plus configuration defaults like wikilinks and automatic internal link updates.
Why separate “Areas,” “Projects,” and “Resources” in an Obsidian second brain?
How does the “inbox” folder prevent notes from getting lost or misfiled?
What are “domain routes,” and how do they change navigation and discovery?
Which configuration choices make the system feel fast and consistent?
How do templates and plugins work together to automate daily capture and task tracking?
Why add date prefixes to Zettelkasten-style notes?
Review Questions
- How does the system ensure meeting notes remain accessible even after a project is archived?
- What workflow role does the inbox play, and when does sorting happen?
- How do domain routes and graph view work together to reveal learning focus and gaps?
Key Points
- 1
Use PARA-style folders—Areas, Projects, Resources—to separate ongoing themes, time-bound goals, and reusable/reference material.
- 2
Route all new notes into an inbox first, then sort them during a weekly review to keep capture and organization reliable.
- 3
Define a small set of Areas and add an inbox as a dedicated capture point for new notes.
- 4
Create “domain routes” so notes connect to recurring interests, and use graph view to see relationships and attention patterns.
- 5
Set Obsidian defaults for speed and consistency: full-width notes, wikilinks (shortest path), inbox as the new-note location, and predictable attachment storage.
- 6
Install a plugin stack that supports navigation and workflow: Kanban for tasks, Periodic Notes for dated pages, Templater for automation, and Workbench for active-note collection.
- 7
Configure Zettelkasten note creation to auto-prefix dates so sorting and timeline tracking happen automatically.