@aviationdoctor.eth
Ok, I've given this more thought and also considered the existing requests on forum.obsidian.md to balance my with popular demand.
## TL;DR
I'd love to see a native mechanism to pull front matter properties into the body of notes. I feel like Bases have made front matter properties so much more semantically relevant — we can now leverage meaningful data about a note stored in a front matter property, such as a short abstract, to be displayed in a table-style Base alongside each filename. Amazingly useful for MOCs, for instance.
## Problem
Bases have exacerbated the following tension: if I store more meaningful data in front matter properties, they still won't show in the body of notes. Duplicating it inside the body would be poor practice. Ideally, we would pull from the front matter properties into the note dynamically; for example, to display the "abstract" property in a callout at the top of the note, or assemble a citation from author, year, and date fields stored in front matter (for bibliographic notes).
## Current workarounds (using a date field as an example)
1. Dataview: Date: `= this.date ?? "Unassigned"`. Downsides: non-core plugin, doesn't work with Publish.
2. Templater: Date: <% tp.frontmatter.date %>. non-core plugin, doesn't work with Publish, not dynamic.
3. Native: {{date}}: not dynamic, doesn't work with Publish.
4. Bases: file.path == this.file.path. Won't simply insert the property within the flow of text due to table, list, or card formatting of the output. Doesn't work with Publish (though on the roadmap).
## Proposal
Either extend the current moustache syntax to all front matter properties (e.g., {{this.file.date}}), or allow for a new "Raw" Bases view type that outputs values with zero formatting overhead, so it can be inserted within a line of text by simply transcluding the Base (e.g., "this note was originally written on ![[related.base]]").
## Downside
I can see syntax like {{this.file.date}} not being Markdown-compliant in the sense that other parsers won't dynamically replace it with data in view mode. But the data that this syntax is calling still exists within the note, just in the front matter above, so no semantic information is lost if the note gets detached/orphaned and migrates to a non-Obsidian system.
## Related
This is related to https://forum.obsidian.md/t/show-display-embed-the-note-properties-within-the-note-body/71004 but back then Bases did not exist as a mechanism for filtering for notes, pulling static properties, and creating dynamic properties with formulas.