Bases: tables & cards
A Base is a database-style view built over your notes' frontmatter properties — a table, a card gallery, or a list that filters and sorts your notes like a lightweight database, while every row stays an ordinary Markdown file.
Once your notes carry properties — typed frontmatter like status, type, date, or rating — a Base turns them into structured, queryable views. It's the difference between a pile of notes and a table you can slice.
Properties come first
A Base is only as useful as the properties it reads. Add frontmatter to the notes you want to organize — for example a status, a type, and a date — and edit those values in the Properties panel. Templates are a good way to make sure every note of a kind carries the same properties. Then point a Base at them.
Bases are parity with Obsidian Bases: views defined over your notes' properties. Because the data is just frontmatter in your .md files, nothing is locked in a separate database — the Base is a lens over files you own.
Build a view
Choose the notes
A Base gathers notes and reads their properties. Scope it to the notes you care about — for instance everything of a given type or in a given area.
Filter
Narrow to what matters: show only status: active, only this quarter's entries, only notes with a given tag or property value.
Sort
Order the results by any property — by date, by name, by status — so the view reads the way you think.
Pick a layout
Present the same notes as a table, a cards gallery, or a list, depending on what you're doing.
Views to reach for
A spreadsheet-like grid: one note per row, properties as columns. Best for scanning and comparing many notes at once — a project tracker, a reading list, a CRM-style contact sheet.
A gallery of cards, one per note. Best when each note deserves a bit of visual room — collections, references, anything you browse rather than scan.
A compact list of matching notes. Best for a focused, filtered feed — today's tasks, open items, recent entries.
Design your templates and your Bases together. If every project note is created from a template that sets status and type, a Base that filters and sorts on those properties stays accurate with zero extra effort.
Related
Organizing your vault
The overview: files, search, bookmarks, daily notes, templates, and Maps & Manuals.
Tags & properties
The frontmatter every Base reads — add and edit the properties your views filter on.
Templates
Make sure new notes carry the right properties from the start.
Maps & Manuals ✦
An index that summarizes an area, not just tabulates it.
Glossary
Base, property, frontmatter, view — defined.