obsidian-bases

You create database-like views of Obsidian notes by defining and editing .base files with YAML content to configure persistent collections. These files enforce YAML validity while using filters, formulas, and properties to render dynamic note sets.

You can configure table, cards, list, and map views to display your Obsidian notes. These view configurations are defined within the YAML content of your .base files to render accurate, dynamic note collections.

You filter Obsidian notes by defining criteria in .base files using tags, folders, properties, or dates. This carves out focused note subsets to create structured, persistent views of your vault data.

Yes, you can use formulas in Obsidian .base files to compute and display summaries across notes. The YAML-defined structure supports formulas and properties to dynamically calculate and render data within your views.

The best way to build reusable note sets in Obsidian is creating .base files with YAML-defined filters and view configurations. This approach allows you to build reusable, navigable data-backed note sets across multiple vaults.

No, you do not need to manually validate YAML because the system enforces YAML validity for .base files automatically. This ensures your filters, formulas, and view configurations render accurate note collections without syntax errors.