Obsidian

What is it

Obsidian is a powerful knowledge base that works on top of a local folder of plain text Markdown files. It features bidirectional linking (wikilinks), a graph view for visualizing connections, and a rich plugin ecosystem. Unlike Notion or Roam Research, Obsidian is entirely local-first—your data lives in plain text files on your computer, not someone else’s server.

My Opinion

Obsidian is what happens when you respect data sovereignty and provide enough features to make power users happy. It’s the antidote to SaaS lock-in, and the tool I use for everything from project planning to this blog. Every concept page you’re reading was drafted in Obsidian before being published here.

The Local-First Philosophy

Obsidian stores your notes as plain Markdown files on your file system. This means:

• You can use any text editor to edit them
• You can version control them with Git
• You can back them up however you want
• You’re not locked into any proprietary format
• The app can be abandoned and you still have your data

This is non-negotiable for me. I’ve lost too much knowledge to platform shutdowns and API changes. With Obsidian, my notes are just files. When I want to publish them, I sync to an Astro blog. When I want AI assistance, I point Claude Code at my vault.

The Wikilink Revolution

Obsidian popularized bidirectional linking for the masses. The [[link]] syntax is intuitive and powerful. When you link from note A to note B, note B automatically shows a backlink to note A. This creates a web of connections that traditional folders and tags can’t replicate.

The graph view visualizes these connections, helping you discover relationships you didn’t know existed. It’s the same principle behind these concept pages—everything links to everything else, creating a knowledge graph rather than a knowledge silo.

The Plugin Ecosystem

The core app is intentionally minimal, but the plugin ecosystem is massive. From LaTeX support to calendar integration, from Kanban boards to advanced graph analysis, there’s a plugin for everything. The community has built an entire ecosystem around this tool, making it flexible enough for personal knowledge management, academic research, and technical documentation.

The Collaboration Gap

This is the one weakness. Obsidian is fundamentally a single-user app. There’s an official Sync service and some community solutions for collaboration, but it’s not designed for team knowledge bases in the way Notion or Confluence are. This is a feature, not a bug—it keeps Obsidian focused on personal knowledge management.

For team documentation, I’d still reach for Confluence (grudgingly) or GitBook. Obsidian is for building your second brain, not a team wiki.

The Publishing Pipeline

Obsidian’s Markdown files are portable by design. I use a sync script to publish my vault to this Astro-powered blog. The wikilinks become HTML links, the images get optimized, and the graph view becomes the concept connections you see here. The pipeline from thought to published content is seamless.

Conclusion

Obsidian is the best personal knowledge base I’ve ever used. The combination of local-first data ownership, powerful linking, and an extensible plugin ecosystem makes it the perfect tool for building a second brain. See my epic series on Obsidian for a deep dive into how I use it for everything from note-taking to blog publishing.