obsidian-frontmatter-sync

Frontmatter schema validation checks Markdown files against a defined schema to ensure required fields exist and defaults apply. This enforces structure across Obsidian vaults before automated publishing or indexing.

Obsidian frontmatter sync pushes changes to external destinations like static site pipelines or content collections. It keeps source and destination frontmatter in sync via the rematter tool during cross-destination workflows.

Renaming frontmatter fields in Markdown collections is handled through bulk update operations that apply changes across many files at once. This maintains consistency across large vaults and repositories without manual editing.

Filename management renames and normalizes filenames to reflect frontmatter state and improve organization. This keeps Markdown file names aligned with metadata changes during bulk vault operations.

Frontmatter schema validation applies to any collection of Markdown files, not just Obsidian vaults. It checks required fields and applies defaults to maintain consistent metadata across large Markdown repositories.