The Case for Plain Markdown as Your Personal Knowledge Base

The core argument here is deceptively simple: your notes should live in a folder of plain markdown files that you own outright, with any app serving as a window into that folder rather than a proprietary vault that holds your data hostage. The durability case for markdown is well-known — readable in any editor, on any machine, with zero software dependencies, for decades. The less-discussed advantage is interoperability: because markdown is just text, every text-based tool already works on it — version control, terminal search, backup software, scripts, and whatever AI tooling emerges next year — without needing any app's permission.

The real intellectual move is flipping the question from 'files vs. app' to 'what should an app add to files without claiming ownership of them?' The answer centers on frontmatter — a small block of structured fields between dashes at the top of a markdown file. That convention, shared across most markdown tools, lets a plain text file double as a task with a due date, a calendar entry, or a board card, while remaining fully readable in any editor. Pellet, a note app built by the author, uses this as its foundation: tasks are notes with fields at the top, not rows in a separate database, and any fields the app doesn't recognize are left untouched — including fields written by other apps sharing the same folder.

The piece lays out a specific checklist for what any serious markdown-based app must deliver: bidirectional links (typing a note name creates a link, and that note shows what links back to it automatically); both folders and tags for organization, with nested tags providing a hierarchy for free; tasks that are full notes you can open, link to, and write inside, viewable as tables, boards, or calendars; fast capture via shortcuts or quick-add boxes; full-text search plus a quick file switcher; support for non-text formats like canvases, drawings, and PDFs stored in open formats; and zero network activity without explicit user consent — no mandatory accounts, no server copies, with any sync being self-hosted and encrypted.

The honest trade-off is acknowledged directly: plain files don't support real-time collaborative editing with colleagues or frictionless browser access, and backup responsibility falls on the user. In exchange, your knowledge base is not merely 'exportable' in some lossy zip format — it is literally the same files, in the same folder, accessible to whatever tool you choose next. That permanence and portability is the proposition Pellet is built around.