Start with a blank slate

Obsidian is a local-first note-taking app, which means your notes live as plain text files on your own computer, not in a cloud server you don't control. This local storage is the core value proposition: you own your data, and it remains accessible even if the company disappears. To begin, download and install Obsidian from obsidian.md. Once installed, open the application to see a clean, empty interface ready for your input.

The first thing you will encounter is the "Create Vault" dialog. A vault is simply a folder on your computer that holds all your notes, attachments, and settings. Think of it as the root directory for your personal knowledge system. You can name it anything that reflects your current focus, such as "Personal," "Work," or "Research."

Click "Create" to initialize the vault. Obsidian will create the folder structure and open the main editor. You are now ready to create your first note. Click the "New Note" button (the plus icon) in the left sidebar, type a title, and start writing. This empty state is intentional; it removes friction and lets you build your system organically as your needs evolve.

Create your first note

Your vault is just a folder on your computer, and the first note is the seed. Obsidian stores everything as plain text files, meaning you own your data completely. There are no servers to sync, no subscriptions to pay, and no vendor lock-in. When you create a note, you are creating a local file that any text editor can open.

Start by clicking the New Note icon in the left sidebar or pressing Ctrl+N (Windows/Linux) or Cmd+N (Mac). A blank page appears, ready for your thoughts. Unlike cloud apps, your work is saved automatically as you type. You don't need to worry about losing progress or hitting a save button.

Use the linking syntax

The real power of Obsidian comes from connecting ideas. To link to another note, type two square brackets [[ followed by the name of the note you want to link to. If the note doesn't exist yet, Obsidian will create it automatically the moment you click the link. This is called a "backlink," and it builds your knowledge graph organically.

For example, type [[My First Note]]. This creates a clickable link. If you hover over it while holding the Ctrl key (or Cmd on Mac), you can preview the content without leaving your current page. This atomic linking approach keeps your notes small and interconnected, making it easier to find connections between disparate ideas later on.

The Web3 Infrastructure Playbook
1
Open the new note command

Click the plus icon in the file explorer or use the keyboard shortcut. A new untitled tab opens, ready for input.

The Web3 Infrastructure Playbook
2
Name your note clearly

Type a descriptive title. Obsidian saves the file as a markdown file with the same name. Clear names help you find notes quickly when your vault grows.

3
Add your first link

Type [[ to start a link. Type the name of an existing note or create a new one. This connects your current thought to your broader knowledge base.

4
Save and verify

Your work is auto-saved. Click the link you just created to ensure it opens the correct note. This confirms your vault is linking properly.

Enable core plugins

Obsidian ships with a powerful set of built-in features that remain disabled by default. Enabling them is the fastest way to transform a simple folder of text files into a functioning knowledge vault. These tools handle the heavy lifting of organization and retrieval, letting you focus on your ideas rather than file management.

The Web3 Infrastructure Playbook
1
Activate the graph view

Navigate to the settings menu and open the Core Plugins panel. Toggle on the Graph View. This feature renders your vault as an interactive network map, showing how your notes connect through links. It provides immediate visual feedback on your growing knowledge base, helping you spot isolated notes or emerging clusters of related topics.

The Web3 Infrastructure Playbook
2
Turn on daily notes

Enable the Daily Notes plugin in the same settings panel. This creates a new note for every day you open Obsidian, automatically formatted with the date. It serves as a central hub for daily logging, quick thoughts, and meeting notes. You can customize the folder location and format to match your preferred workflow, ensuring all time-sensitive entries are captured consistently.

The Web3 Infrastructure Playbook
3
Configure note templates

Activate the Templates plugin to streamline your note creation process. Create a folder for your templates and define standard structures for recurring note types, such as meeting summaries or project briefs. When creating a new note, use the template command to insert these structures instantly. This consistency reduces friction and ensures every note contains the metadata you need for future retrieval.

4
Set up the command palette

Familiarize yourself with the Command Palette, accessible via a simple keyboard shortcut. It acts as a central control panel for every action in Obsidian, from opening files to running complex searches. Learning to navigate via the palette rather than clicking through menus significantly speeds up your workflow, allowing you to keep your hands on the keyboard and your mind on the content.

With these core plugins active, your vault is no longer just a storage bin. It becomes an active thinking tool that connects your daily observations with your long-term projects. This foundation supports the local-first data ownership model, ensuring all your insights remain accessible and under your control without relying on external servers.

Avoid folder overload

The easiest mistake with OBSDN is comparing options on the most visible detail while ignoring the day-to-day constraint. A choice can look strong on paper and still fail because it is too hard to maintain, too expensive to repeat, or awkward in the actual setting. Use the same checklist for every option: fit, cost, durability, timing, upkeep, and fallback plan. That keeps the comparison practical instead of drifting into preference alone.

The simplest way to use this section is to keep the setup small, verify each change, and record the stable configuration before adding optional accessories.

Install community plugins

Your vault is functional, but the community plugins are where it truly comes alive. Think of the core app as a sturdy bicycle and these plugins as the specialized attachments—a cargo rack, better gears, or a GPS. They extend what Obsidian can do without changing the fact that your data stays local.

We will install a template manager and a calendar. These two tools solve the most common friction points for new users: remembering what to write and keeping track of when.

1
Enable the community plugins setting

Before you can install anything, you need to enable unsafe mode. Go to Settings (the gear icon) > Community plugins. Toggle Unsafe mode to on, then click Turn on. This tells Obsidian you trust the source of the plugins you are about to install. Without this step, the install button will remain greyed out.

2
Install Templater

Search for Templater in the plugin browser. Unlike the basic Obsidian templates, Templater lets you insert dynamic content like the current date, file name, or even run simple JavaScript. Click Install, then Enable. It is the most robust template engine available for the platform.

3
Install Full Calendar

Search for Full Calendar. This plugin replaces the default weekly view with a fully interactive calendar that syncs with your notes. Click Install, then Enable. It provides a visual anchor for your daily notes, making it easier to see how your writing schedule fits into the week.

4
Configure your first template

Create a new folder in your vault named _Templates. Open Templater settings and set this folder as your Templates folder. Create a new note inside called Daily Note. Add a simple header with <!-- <% tp.date.now("YYYY-MM-DD") %> -->. This ensures every new daily note starts with the correct date automatically.

With these two plugins active, your vault shifts from a static folder of files to an active workspace. You have the structure to write and the calendar to track it, all while keeping your data entirely on your own device.

Avoid setup traps

It is easy to get caught up in the mechanics of building a vault and lose sight of the purpose. The most common mistake is over-engineering the structure before you have written anything. Beginners often spend weeks designing complex folder hierarchies and plugin configurations. This approach slows down progress and makes the system feel rigid. Your vault should feel like a workshop, not a museum. Keep the initial structure simple and let it evolve as your notes grow.

Another frequent error is syncing too early. Many users enable cloud sync immediately after installing the app. If you sync a vault that is still in its messy, early stages, you risk propagating errors across all your devices. It is better to spend the first few days organizing your notes locally. Once you have a stable, clean set of files, you can safely enable synchronization. This ensures your cloud backup reflects a functional system rather than a work in progress.

The Web3 Infrastructure Playbook

OBSDN Setup Checklist

Before you start building out your knowledge base, run through this quick verification. It ensures your local-first vault is secure, organized, and ready for daily use without unnecessary complexity.

The Web3 Infrastructure Playbook
  • Vault Created: Confirm your folder exists in a safe, backed-up location (e.g., iCloud, Dropbox, or local drive).
  • Core Plugins Enabled: Turn on "Daily Notes," "Outline," and "Backlinks" in Settings > Core Plugins.
  • Default Location Set: Ensure new notes open in your main vault folder, not a subfolder.
  • Graph View Visible: Open the Graph View to confirm your empty or initial notes are rendering correctly.
  • Search Tested: Type a test note title to verify full-text search is indexing your content immediately.

Once these boxes are checked, you have a functional foundation. You can now focus on writing rather than troubleshooting.

Frequently asked: what to check next