Obsidian for Beginners: The Complete Step-by-Step Guide to Building Your Personal Knowledge Management System cover

Fiction

Obsidian for Beginners: The Complete Step-by-Step Guide to Building Your Personal Knowledge Management System

by lk v

3 chapters17 min read

Chapter 1 illustration

Chapter 1

Getting Started with Obsidian

Alex Rivera stared at the blinking cursor in the center of their screen, surrounded by a chaotic sprawl of open browser tabs, half-finished design mockups, and a desktop littered with files named things like "final_FINAL_v3_ACTUALLYFINAL.psd" and "client_notes_june.txt." They ran a hand through their hair, the familiar frustration tightening in their chest. Another project idea had slipped through the cracks — this time, a color palette concept for a rebrand pitch that had come to them mid-walk, now lost somewhere between the coffee shop and their apartment.

"Seriously, how do people keep track of all this?" Alex muttered, more to themselves than to the empty room.

A chime from their phone pulled them from the spiral. A message from Sam Chen: Hey, saw you were struggling with note chaos again. You ever try Obsidian? It’s been a game-changer for me. Free, lightweight, and it actually connects your ideas. DM if you want the link — happy to walk you through it.

Alex’s thumb hovered over the screen. They’d heard of note-taking apps before — Notion, Evernote, even the old-school simplicity of plain text files — but nothing had stuck. The learning curve always felt steeper than the payoff. Still, Sam’s message carried none of the pressure they’d felt with other recommendations. It was just an offer, low-stakes and genuine.

What’s the worst that could happen? they thought. I try it for twenty minutes. If it’s another dead end, I delete it and move on.

They clicked the link Sam sent: obsidian.md. The page loaded cleanly — no flashy animations, no pop-ups begging for a subscription. Just a clear headline, a short paragraph about a "second brain," and a prominent download button for Windows. Alex’s laptop whirred softly as the installer downloaded, the progress bar inching forward with a quiet inevitability.

When the file finished, they double-clicked it. The setup wizard was straightforward — next, agree, install. No optional toolbars, no bundled software. Just Obsidian, being installed into their Programs folder like any other tool they used for work: Photoshop, Illustrator, Figma. Familiar, almost comforting in its simplicity.

Done, Alex thought, a flicker of something like hope stirring. Now what?

They launched the app from the Start menu. A window opened, split into two halves. On the left, a panel titled "Vault" with a button that said "+ New Vault." On the right, a welcome message: Welcome to Obsidian. Your thoughts, connected.

Alex’s breath caught slightly. It felt… intentional. Not overwhelming. Not trying to do everything at once. Just a space waiting to be filled.

They clicked "+ New Vault."

A dialog box appeared. Vault name: they typed Knowledge Hub. Location: they clicked the folder icon and navigated to their Desktop, then made a new folder inside it called the same name — Knowledge Hub — and selected it. Below, a toggle labeled "Create from template" was switched off. Alex left it that way. Sam had said to start empty, to learn the shape of the tool before trying to fit into someone else’s structure.

Better to build my own system, they thought. Even if it’s messy at first.

They clicked "Create."

The welcome panel slid away, replaced by three empty panes. The left sidebar — the file explorer — showed only the vault name at the top, with nothing beneath it. The center pane was a blank editing window, a faint placeholder text blinking: Start writing here… The right sidebar remained collapsed, its icons dimmed but present: a bullet list outline, a graph view, a tag panel.

Alex sat back in their chair, the creak of the leather familiar. The screen reflected in their glasses — a clean interface, waiting. No files. No clutter. Just the quiet promise of a place to begin.

A clean interface offers the quiet promise of a fresh start.
A clean interface offers the quiet promise of a fresh start.

They hovered their mouse over the file explorer, then clicked the "+" icon that appeared when they hovered over the vault name. A prompt: New file. They typed first note.md and pressed Enter.

The center pane shifted instantly to show the new file, the cursor blinking at the start of a fresh line.

Alex took a slow breath. Their fingers found the keyboard.

Today, they typed, I started something new.

They didn’t know yet how far this would go. But for the first time in weeks, the scattered pieces didn’t feel like a failure. They felt like raw material.

And that was enough to begin.

Alex Rivera leaned forward, the cool glass of their untouched coffee warming their palms as they studied the Obsidian window. The interface felt sparse but deliberate, each pane a quiet invitation. Their eyes traced the divisions: a narrow column on the left labeled "Knowledge Hub" at the top, a wide central space where their first note lived, and a thinner strip on the right with faint icons — a bullet list, a interconnected web, a tag.

"Three panes," they murmured. "Left is the file explorer, center is where I write, and the right… that’s for extra views?"

A soft chime sounded. Sam’s video call request blinked in the corner of their screen. Alex accepted, and Sam’s face appeared, calm and encouraging.

"Exactly," Sam said. "Think of it like your desk. Left is your filing cabinet, center is your workspace, and right is where you put tools you might need — like an outline or a map of how your notes connect."

Alex nodded, clicking the bullet list icon in the right sidebar. The pane shifted, displaying a hierarchical view of their single note: first note.md with no subheadings yet.

"It’s showing the structure," Alex observed. "Even though there’s nothing but the first line."

"Exactly," Sam replied. "It builds as you add headings. Try it."

Alex pressed Enter after their opening line, then typed a second line: I’m trying something new to keep my ideas from slipping away. They highlighted the text and clicked the "B" icon in the toolbar above the editor. The letters darkened instantly.

"Bold works," they said, smiling slightly. "Now, how do I see what this looks like without the markup?"

"Preview mode," Sam said. "Look at the toolbar — there’s an icon that looks like an eye. Click it."

Alex hovered over the icons until they found one resembling an eye with a slash through it. They clicked it. The asterisks around their bolded text vanished, and the words appeared clean and weighted, as if printed.

Alex sees formatted text appear with a click — like magic.
Alex sees formatted text appear with a click — like magic.

"Whoa," they breathed. "It’s like magic. One click and I see the formatted version."

"Click it again to go back to editing," Sam instructed. Alex did, and the markdown syntax returned. "That toggle lets you write in plain text and instantly check how it’ll look. Super useful for catching formatting errors."

Alex experimented, adding a dash and a space to create a bullet point, then switching to preview to see it render properly. They felt a spark of satisfaction — tangible, immediate feedback.

"Now, what about hiding these sidebars?" Alex asked, gesturing to the left and right panes. "Sometimes I’ll want just the editor."

Sam pointed to the three vertical dots in the top-right corner of each sidebar. "Click those, and you’ll see options to collapse or expand. Or use the keyboard shortcuts — Ctrl+Shift+F for file explorer, Ctrl+Shift+R for right sidebar. But the dots work fine to start."

Alex clicked the dots on the left sidebar and selected "Collapse." The file explorer slid away, leaving more room for the editor. They did the same on the right, leaving only the central pane and a slim toolbar at the top. The screen felt expansive, focused.

"Nice," they said. "It’s like clearing my desk to work on one thing."

They restored both sidebars, then clicked the gear icon in the lower-left corner — the settings menu. A new window opened, filled with tabs: Appearance, Files & Links, Hotkeys, and more.

"Careful not to get lost in here too early," Sam warned gently. "Settings are powerful, but you can break things if you tweak the wrong thing. For now, just know it’s there. You’ll want to come back later to change themes or adjust how links work."

Alex skimmed the Appearance tab, noticing a toggle for "Dark mode." They switched it on, and the interface shifted to deep grays and blues, easier on their tired eyes.

"Better," they murmured. "Less glare."

Sam smiled. "See? Small adjustments make it yours. But remember — the vault is just a folder on your computer. Obsidian doesn’t lock your data in. Your notes are plain .md files, right where you put them."

Alex glanced back at the left sidebar. Their vault name sat at the top, and beneath it, first note.md waited. They right-clicked the file and selected "Reveal in file explorer." A window popped open, showing the file nestled inside the Knowledge Hub folder on their Desktop.

"It’s really just a text file," they realized, a hint of awe in their voice. "But with superpowers."

"Exactly," Sam said. "The magic isn’t in the file format — it’s in how Obsidian connects them. But we’ll get to that tomorrow. For now, you’ve got the layout down. You can write, preview, hide what you don’t need, and find your way back."

Alex leaned back in their chair, the leather creaking softly. The Obsidian window glowed softly in the dimming afternoon light, the three panes now familiar landmarks. They weren’t just seeing an interface anymore — they were seeing a workspace taking shape.

I can do this, they thought. One pane, one note, one click at a time.

Chapter 2 illustration

Chapter 2

Building Your First Notes

Alex opened Obsidian and glanced at the left sidebar where their vault, Knowledge Hub, rested at the top. Beneath it, first note.md sat like a bookmark in a well-worn novel. The afternoon light had softened, casting long shadows across the desk, and the dark mode interface glowed gently on the screen. They clicked the plus icon at the top of the file explorer.

A small dialog appeared, cursor blinking in the field labeled "New note name." Alex typed Project Phoenix Brief and pressed Enter. The file explorer scrolled to highlight the new note, and the center pane cleared, ready for input.

They began typing, using the hash symbol to create a heading.

Project Phoenix Brief

Below it, they added a subheading for client details.

Client: Veridian Dynamics

Alex pressed Enter and started a list, using hyphens for each bullet point.

  • Initial meeting: Tuesday, 10 AM
  • Deliverables: Logo suite, brand guidelines, social media kit
  • Budget: $12,000
  • Timeline: 6 weeks

They highlighted the word "Logo suite" and pressed Ctrl+B. The text darkened and thickened, wrapped in double asterisks as Logo suite. A smile touched their lips. It felt like using a highlighter on paper, but cleaner, reversible.

Alex applies bold formatting with a keyboard shortcut.
Alex applies bold formatting with a keyboard shortcut.

Next, they toggled to preview mode by clicking the eye icon in the toolbar. The raw Markdown vanished, replaced by clean, formatted text: a bold heading, a subheading, and a bulleted list with one item emphasized. They switched back to edit mode to make a tweak.

Alex added another bullet under deliverables, italicizing a phrase for nuance.

  • Deliverables: Logo suite, brand guidelines, social media kit preview, social media kit

They saved nothing explicitly — Obsidian had already done it in the background. Curious, they right-clicked the note in the file explorer and chose "Reveal in file explorer." A window opened, showing the Desktop, the Knowledge Hub folder, and inside it, a file named Project Phoenix Brief.md.

Alex opened it in Notepad to confirm. The text appeared exactly as typed: hashes, asterisks, hyphens, and all. No hidden formatting, no proprietary code. Just plain Markdown, resting where they’d put it.

They closed Notepad and returned to Obsidian. The note was still open, the cursor waiting. Alex took a breath, feeling the quiet thrill of creation — not just writing, but building something that would last, connect, and grow. They typed one more line, a reminder to themselves.

  • Next step: Sketch three logo concepts by Friday

Then they paused, hands resting on the keyboard, watching the blinking cursor pulse in the dim light. The note was small, but it was theirs. And it was real.

Alex leaned back in their chair, the soft hum of the laptop fan the only sound in the quiet apartment. The cursor blinked at the end of the line in Project Phoenix Brief.md, waiting. They had just confirmed that their first note lived as plain text on their desktop, a small victory that felt disproportionately large. Now, with the basics of formatting under their fingers, they wanted to see how notes could talk to one another.

They clicked the plus icon again in the file explorer. This time, they typed Client Feedback Notes and pressed Enter. The new note opened in the center pane, empty and ready.

Alex began typing, recalling a recent call with Veridian Dynamics.

Client Feedback Notes

Meeting: Thursday, 3 PM

  • Presented three logo concepts
  • Client preferred the bold, geometric option
  • Noted concern about scalability for favicon
  • Requested variations with secondary colors
  • Action: Refine selected concept by EOD Monday

They paused, then added a line at the bottom, thinking of the brief they’d just made.

See also: [[Project Phoenix Brief]]

As they typed the closing brackets, the text shifted — the double brackets faded, and the words turned blue, underlined faintly. A link. Alex hovered the cursor over it; a small preview popped up, showing the first few lines of the brief. They clicked. The center pane swapped instantly to Project Phoenix Brief.md, the bold heading and bulleted list flooding the screen. A grin spread across their face. It worked.

They clicked the back arrow in the top-left of the editor and returned to Client Feedback Notes. The link remained, solid and clickable.

Next, they created another note. This one for the visual scraps they’d been collecting — color palettes, typography pairings, logo sketches that caught their eye during late-night browsing.

They clicked the plus icon once more, typed Design Inspiration, and hit Enter.

Design Inspiration

Source: Dribbble, 4/5

  • Geometric logo with negative space arrow
  • Bold sans-serif paired with delicate script
  • Deep navy and gold color scheme
  • Circular emblem with modular elements

Alex scrolled up, then added a line beneath the title.

Related to: [[Project Phoenix Brief]]

Again, the text transformed into a clickable link. They tested it — clicked, jumped to the brief, clicked back. The connection felt intentional, like threading a needle through fabric.

They wanted to see it all together. Alex clicked the icon in the top-right of the sidebar — a circle surrounded by smaller circles, the graph view. The right pane shifted, replacing the outline and tag panels with a dark canvas dotted with nodes and lines.

Three circles appeared, each labeled with a note title. Project Phoenix Brief sat slightly left of center. Client Feedback Notes hovered above and to the right, Design Inspiration below and to the left. Lines connected each of the two newer notes directly to the brief — no line between the feedback and inspiration notes, as Alex hadn’t linked those yet.

Alex leaned forward. The graph was simple, but it was theirs. Each node a thought, each line a relationship forged by double brackets. They clicked on Client Feedback Notes in the graph; the note opened in the center pane. They clicked Design Inspiration — same result. The brief remained the hub.

“It’s like a map of your mind,” Sam’s voice echoed from earlier that day, when they’d shown Alex the graph during their video call. “You don’t just store notes — you grow a network.”

Alex views the growing network of notes in graph view.
Alex views the growing network of notes in graph view.

Alex sat still, watching the gentle pulse of the selected node in the graph. The afternoon light had faded completely; the desk was lit only by the screen’s dark mode glow. They hadn’t realized they’d been holding their breath.

They reached up and rubbed their eyes, then smiled. It wasn’t much — three notes, two links — but it was a start. A structure. A way to hold ideas not in isolation, but in conversation. The vault wasn’t just a folder anymore. It was a space where meaning could emerge from connections.

Alex closed the graph view and returned to the editor. They typed one final line in Design Inspiration, beneath the list.

Next: Sketch variation using this color scheme [[Project Phoenix Brief]]

The text turned blue as they finished the closing bracket. They didn’t click it yet. They let it sit — a promise, a direction.

Outside, the city lights began to flicker on. Inside Knowledge Hub, a small network glowed quietly, waiting to grow.

Chapter 3 illustration

Chapter 3

Establishing a Working Knowledge System

Alex stared at the graph view on their screen, the faint blue lines between nodes pulsing softly in the dark mode glow. The connection between their three design project notes felt fragile but real—a thread they could follow. Sam’s voice came through their headphones, warm and encouraging. “See? That’s the foundation. Now imagine doing that every day, not just for big projects, but for the little things too—ideas that pop up in the shower, meeting notes, random thoughts. That’s where daily notes help.” Alex nodded, even though Sam couldn’t see them. “So it’s not just about linking what I already know. It’s about catching what I might forget.” “Exactly. And Obsidian makes it easy to start.”

Alex opened the settings pane with Ctrl+, and scrolled to the Community Plugins tab. Safe mode was still on, a remnant of Sam’s early warning not to tinker too soon. They flipped the switch, read the prompt, and clicked Enable anyway. A list of plugins appeared, and they typed “Daily Notes” into the search bar. The first result had a clean icon and a description that matched what Sam described: Automatically creates a note for each day. They clicked Install, then Enable. A new ribbon icon—a calendar—appeared on the left sidebar. Alex hovered over it, then clicked.

A prompt asked where to save daily notes. Alex chose the default: a new folder inside the vault called daily notes. They named the format YYYY-MM-DD so the files would sort chronologically. After confirming, Obsidian created today’s note: 2024-06-10.md. It opened in the editor, blank except for the date at the top in large text.

Alex began typing. Morning standup with client: confirmed logo revisions due Thursday. Idea: try asymmetrical balance in the hero section—sketch after lunch. Follow up: send font options to Maya by 3 PM. They hit Ctrl+S, though they knew it wasn’t necessary—Obsidian had already saved it silently in the background.

The next morning, Alex opened Obsidian before coffee. The daily note for June 11th was already waiting. They added: Dreamt about a font that looked like wind—note to explore organic typefaces later. Meeting with Sam at 2: review portfolio site. #idea #design

They paused at the hashtags. Sam had mentioned tags during their last call—lightweight labels that lived inside the note, not in the folder hierarchy. Alex tried it on a whim, tapping # and typing idea. The text turned faint blue, underlined. They added design after a space. Instantly, the sidebar updated: a Tags pane appeared, showing both tags with a count of one each.

Alex discovers the power of tags to link ideas across notes.
Alex discovers the power of tags to link ideas across notes.

Alex clicked #idea. The note they’d just written appeared in the preview pane, highlighted. They smiled. No folders to manage, no moving files—just a label that worked across the vault.

Later that week, after accumulating five daily notes and three project notes, Alex felt the need for broader structure. They opened the file explorer and right-clicked in the vault root. New Folder They named it Projects and dragged in the three design notes. Another folder: Resources, for inspiration links and article clippings. A third: Archive, for old versions and completed work.

They opened a daily note from two days prior and added a link to a resource note: Found this color palette on Dribbble—see [[Resources/color inspiration]] The text turned blue, and when they hovered, a preview popped up showing the note’s contents.

Alex didn’t overthink it. The system wasn’t perfect—some notes lived in daily notes, others in folders, tags floated freely—but it worked. Each morning, they opened the day’s note and dumped in whatever had surface: a task, a fragment, a question. Tags helped them find related ideas later. Folders kept active work from getting lost in the noise.

At the end of the week, Alex leaned back. The screen cast a cool glow on their face. The vault wasn’t elegant, but it was alive—growing with every keystroke, every connection, every tagged thought. They weren’t just storing information anymore. They were tending it.

Sam sent a message later that evening: How’s the system feeling? Alex typed slowly, choosing their words. It’s not just a place to put things. It’s where they start to talk to each other. They hit send, then opened today’s daily note and added one last line before shutting down: Today, I felt like I was finally building something that could last.

Alex opened Obsidian on Monday morning, the screen casting a soft glow across their desk. A notification from Sam blinked in the corner: Ready for day one? They smiled, typed back Let’s go, and turned to the day’s note—2024-06-17.md—already waiting in the daily notes folder.

The challenge was simple: each day, a small, focused task to build the habit without overwhelm. Day one: create three notes and link them. Alex began with a fleeting idea from breakfast—a shade of blue that reminded them of ocean fog. They made a new note: Color exploration – ocean fog.md. Inside, they typed: Cool, muted blue-gray. Try in background layers for depth. Then, linking to their ongoing work: See [[Project Phoenix Brief.md]] for context. The text turned blue, and a preview showed the project’s goals when hovered.

Next, a client note: Call with Maya – logo feedback.md. They captured action points: Maya prefers circular variants; test scalability at 16px. Linked to the color note: See [[Color exploration – ocean fog.md]] for palette options. Finally, a resource: Article – Gestalt principles in UI.md, pasted from a bookmark, with a link to the logo note: Relevant to [[Call with Maya – logo feedback.md]].

By lunch, the three notes formed a triangle in the graph view—tiny, but connected. Alex watched the blue lines pulse as they switched between notes, feeling the quiet satisfaction of structure emerging from chaos.

Tuesday’s task: tag everything from yesterday. Alex opened each note and added tags with intention. The color note got #color and #exploration. The client call: #client-feedback and #logo. The article: #design-theory and #reference. As they typed, the tags pane on the right updated in real time, counts climbing beside each label.

They clicked #design-theory. Two notes appeared—the article and, unexpectedly, an older daily note from June 12th where they’d jotted: Read something about visual hierarchy today. Alex opened it, saw the connection, and smiled. The system was already whispering back.

Wednesday: explore the graph view with purpose. Alex opened the graph, zoomed out, and hovered over nodes. The daily notes formed a spine down the center, with project and resource notes branching off like ribs. They noticed a cluster around #idea—five notes linked, from font dreams to sketch concepts. Clicking one highlighted its neighbors, revealing a loose web of creative sparks.

“It’s not random,” Alex murmured. “It’s me.”

Thursday: use a template for consistency. They’d seen Sam use meeting templates and decided to try. In Settings > Templates, they created a simple one:

Meeting with {{title}}

Date: {{date}} Attendees: Agenda: Action items:

  • [ ]

They saved it as Meeting Note. Then, in a new daily note, typed /template and picked it. The structure appeared, ready to fill. For a call with a potential client about brochure design, they filled in the details, tagged it #client-meeting and #brochure, and linked to the Resources folder where they’d saved a competitor analysis.

The template didn’t feel rigid—it felt like a scaffold. By Friday, they’d used it three times, each meeting note now a reliable node in the vault.

Saturday: review and refine. Alex opened the file explorer and scanned the vault. Twenty-three notes now lived in folders or as daily notes. They opened the #idea tag and saw twelve notes—some raw, some developed. One from June 10th: Dreamt about a font that looked like wind. They opened it, added a link to a new note: Font exploration – organic forms.md, and typed: Start with calligraphic bases, explore variable weight. Then tagged it #font and #exploration.

They did the same for #design-theory, connecting two older notes to a new summary: Key principles from reading.md. Each link strengthened the web. Each tag clarified a theme.

Sunday morning, Alex sat with coffee, the vault open on half the screen, the graph view on the other. Over twenty notes. More than thirty links. Tags like #client-feedback, #font, and #meeting-note glowed in the sidebar, each with meaningful counts. The system wasn’t just storing—it was suggesting. When they typed font in a new note, Obsidian suggested [[Font exploration – organic forms.md]] before they finished.

Alex reviews their growing knowledge system, alive with connections and tags.
Alex reviews their growing knowledge system, alive with connections and tags.

Sam’s message came: Day seven. How do you feel?

Alex looked at the screen—their notes, their links, their tags—then typed slowly: Like I’ve built a home for my thoughts. Not perfect, but mine. And it’s ready for more.

They hit send, then opened today’s daily note and added one final line before closing the laptop: Today, I didn’t just take notes. I tended a garden.

The screen dimmed. The vault stayed open, waiting.

ContentsThe end