Generalized front-matter metadata

i know it’s a common feature request (see here and here and here) but i feel i have to summarize the topic:

we can’t rely on filesystem for dates (they get lost when moving/git synced), even worse we can’t have the date in the filename (diaries need at least yyyy-mm-dd_my_title or we need dates in other contexts). also titles can’t get read just by filenames, and if we want to reorder content, or export to other systems (i use Latex and Hugo, for example) there should be a “weight” field. Last the kind of note we are dealing with.

if Obsidian aims to become a “knowledge IDE” i think it would be better to declare “official” some of these fields. so that plugins can start to use them without inventing each an own system, like they are doing now.
we could have the calender Plugin ro read the “date” field, instead of the filename. bartender use the weight to sort files, everything would use the Title field (if defined) to show note’s title instead of the filename…

what i feel are the more requested standard fields are:

  • title (to be used everywhere, navigation, graph, links)
  • date (creation or generic date)
  • updated (when the note was updated)
  • weight (to sort with siblings)
  • type (to declare if the note has a specific template/bahaviour/model) to not be confused with tags which are more about the content.

or do you prefer these fields to be always custom defined by users and plugin developers?

1 Like