obsidian-properties

Consistent YAML frontmatter properties are enforced by defining standard property types (text, list, number, checkbox, date) and using the update_frontmatter tool for safe edits. This maintains uniform data structures across notes and improves vault-wide searchability.

Obsidian frontmatter supports defining property types including Text, List, Number, Checkbox, Date, Date & Time, and Tags. Assigning specific types ensures your YAML metadata remains structured and queryable within Bases and search workflows.

This approach supports both YAML and JSON frontmatter formats in Obsidian. It provides best-practice guidance for managing standardized properties regardless of format, ensuring compatibility with templates and vault automation workflows.

To safely edit frontmatter properties without breaking your vault, always use the update_frontmatter tool. This method enforces safe edit commands and maintains unique property names, preventing data corruption across your notes.

Yes, standardized frontmatter properties integrate directly with Obsidian Bases and Templates. This integration enables vault-wide filtering, templated note creation, and automated workflows based on consistent metadata fields like tags and aliases.

The best way to manage default frontmatter conventions is to establish unique property names and standard types (text, list, date) within your templates. Using the update_frontmatter tool ensures these defaults are applied safely and consistently across new notes.