Template field on type definitions

[dsebastien]

It would be useful to have an optional template field for file scaffolding.

name: meeting-note
template: _templates/TPL Meeting.md

Many markdown-based tools support template systems. Standardizing the reference location helps interop between tools (e.g., Obsidian Templater, Obsidian CLI, ...).

Spec section: Type Metadata

[callumalpass]

Thanks @dsebastien. This is a reasonable idea and sits in a slightly different category from the icon request--there's a concrete action a tool can take with a template pointer (e.g., use the file as starting content for new records), whereas icon is more a presentation issue.

That said, I'm hesitant to add it to the spec right now for a similar reason: template files are tool-specific in their content (Templater syntax, neovim snippets, etc.), so even with a standardized path field, it seems to me that interopability will remain an issue. And since strict: false is the default, any implementation can already read template: from type definitions today as a convention.

That said, I feel like there will be value in something like this. I'll leave it open for further consideration.

[dsebastien]

Indeed interoperability will remain an issue for something like this, I agree. Although just having the field specified (openly without a specific type) would allow implementations to handle it as they want, while at least standardizing on a field name for it