#35

Thanks! I took a look and this really looks useful…

1 Like
#36

+1 For this. I imagine there are multiple ways of having something work, but something well done here could be great. For example, maybe replacing [[]] with a different symbol in the frontmatter. Even something ugly like escapes could be fine at this point.

There’s been some discussion on the Metatable github page, but the solution should really be implemented directly in Obsidian, for the ability to get backlinks.

2 Likes
#37

Hi, was this ever further addressed by any devs?

#38

The last I saw in the forum was that [“Link Name”] would be supported (as that is consistent with YAML syntax). Discord

But it feels like a lot of folks have moved on to using inline dataview fields elsewhere in their documents for links.

1 Like
#39

Can’t wait, honestly!

1 Like
#40

This feature makes sense, and it is essential to my workflow. I do not think that adding another block for metadata is a solution.
Specifying the relations in the body of the note feels forced to me, and I’ll stick with logseq as it does support links in the YAML frontmatter till this feature is implemented.

#41

Bumping this up again because the use of links in YAML is quite important to my workflow as well. Also, being able to pull-down a search for available pages like we do with [[]] with YAML link syntax → [""] would be great.

6 Likes
#42

+1 to this, it’s essential to what I’m trying to accomplish

#43

Any news ? This is a very important feature request, I really hope this gets implemented soon.

2 Likes
#44

I really like your example:

I usually start my notes with an H1 for the note title (so placed below your red line).

I would also like to have a header in Your Block, so I can fold/unfold Your Block for less clutter, when viewing my note.

I therefore wonder if it conflicts with also having a H1 in the Your Block section?

In other words, does it conflict anywhere if I have two H1’s in one note?

Or should it be a H2 in the You Block section or does it conflict to have an H2 above a H1?

Or should the Your Block section not include a header at all?

#45

You can use H1, H2 or whatever you want. No problem.
I personally use this template for my notes:

---
aliases: []
tags: []
---
sources:: []()
***

# Content Begins
1 Like
#46

Thank you for sharing.

  1. So in your case your can’t fold your on block?

  2. Is there any other way to make your block section fold without giving it a header above “sources::”?

  3. Is *** a different way to write a horizontal rule, just without the need of blank lines above and below?

  4. and just out of curiosity: how do you personally write multiple tags in your YAML? And do you use put your tags in " ? And with a # or not?

#47

Hi @WhiteNoise,

this may be a stupid question but anyhow. What is the advantage to use the info on sources as inline meta data (sources::)?

Best regards

#48

@SamAdams, One reason would be the limitations on using links in YAML front matter.

See for example explanation in:

And in:

#49

Hi @Birgitte,
Thanks for the clarification. :+1:

#50

Currently if I define

---
url: https://someurl.com
---

it will be interpreted as a URL (it will be shown as a link, not just a string). Same could be applied to [[]] notation, and we still have the benefit of autocomplete, something that won’t be available with alternative notations.

1 Like
#51

Is the :: in sources:: using some sort of syntax for something or is that just your personal choice.

@SamAdams seems to think it’s “inline meta data” but I personally haven’t seen that syntax before and I don’t see it adding anything when I put it in my vault.

#52

@DandyLyons - the key:: value syntax is used for the “Dataview” Obsidian community plugin: GitHub - blacksmithgu/obsidian-dataview: A high-performance data index and query language over Markdown files, for https://obsidian.md/.

2 Likes
#53

Apologies if I’ve missed mention of this somewhere above, but why isn’t "[[…]]" the least bad option for syntax?

---
Link: "[[Note with \"Double Quotation Marks\" in Title#Heading|Display Text]]"
---

is valid YAML. Ideally Obsidian’s wikilink autocomplete function would detect that the context is a YAML header and escape the necessary characters.

Wikilinks in YAML headers simply being Command-clickable in edit mode would go a long way for me.

See also: Can [[wikilink]] in YAML ever be “done right”? NO. But there could be a “route of least pain”.

Use YAML Frontmatter to define variables in the md document
#54

Hello, @WhiteNoise

Toying with this issue in my own notes. What is the advantage of having both a YAML block and a personal block?

Why not just use the personal-block double-colon format throughout and dispense with the separate YAML block?

Thanks

Angel