@@jun6lee I did consider adding :: inline metadata with the search and replace feature in Visual Code but ended up opting for properties up the top for more control.
@Bos_roseus: That was my main concern also. Dataview can see it but Obsidian Core can't. I decided to make a small mention of inline metadata at the end of the video as I have a feeling it was going to be mentioned in the comments :)
Very helpfull! Thank you. Can you maybe also show / instruct on 'Spaces'? I am struggeling because they seems to be also properties. Any way, again thanks for this video!
Thank you Silvio. I use a combination of the Minimal Theme + Minimal Theme Settings, Style Settings Plugins and Custom CSS Snippets for Tables. Only use CSS for my LifeOS but the rest of the vault uses the Minimal Theme :)
i just notice but how did you make the link in yaml turn into actual link when in reading mode? coz mine don't even when i type it in like you did in the video
Instead of adding the Link in Source Mode, see if you can add it in the Live Preview. Inside the Property Field, start typing [[ then the name of the note you want to link to. Choose the note and Obsidian with auto format the YAML for you. Make sure the note you're linking to exists. Do you show your properties in your Note?
This looks cool but I don't have the properties you have, how can I have those? Should I delete types.json or how can I make it generate a new one or a correct one? The properties I see are: aliases link links tags cssclasses excalidraw-autoexport excalidraw-border-color excalidraw-css excalidraw-default-mode excalidraw-embeddable-theme excalidraw-export-dark excalidraw-export-embed-scene excalidraw-export-padding excalidraw-export-pngscale excalidraw-export-transparent excalidraw-font excalidraw-font-color excalidraw-link-brackets excalidraw-link-prefix excalidraw-linkbutton-opacity excalidraw-mask excalidraw-onload-script excalidraw-open-md excalidraw-plugin excalidraw-url-prefix
Ok after few hours of banging my head I think I solved: - Removed all properties from all notes (not many as the vault is new) - Unassigned all that I'm allowed to, remains aliases, cssclasses and tags - Now the types.json is finally very empty and clean - I am able to add new properties from the code view
Hi Riccard, anything with prefix excalidraw is related to the Excalidraw plugin. YAML Properties are added to Markdown Notes (.md files) Happy you were able to work it out but still a little confused why you're making changes to .json file Doc - help.obsidian.md/Editing+and+formatting/Properties
it'is the video I was looking for ! thanks! clarity and well presented
Just a note to add. You could use :: instead of single if you don't want to move it up to properties up top.
@@jun6lee I did consider adding :: inline metadata with the search and replace feature in Visual Code but ended up opting for properties up the top for more control.
It depends, if you put your tags inline like that
tags:: my_tag
Dataview can see it but not the Obsidian core
@Bos_roseus: That was my main concern also. Dataview can see it but Obsidian Core can't. I decided to make a small mention of inline metadata at the end of the video as I have a feeling it was going to be mentioned in the comments :)
Very helpfull! Thank you. Can you maybe also show / instruct on 'Spaces'? I am struggeling because they seems to be also properties. Any way, again thanks for this video!
Hi Rogier, are you referring to spaces in YAML or the folder spaces?
Thank you for this video Paul. A question unrelated to the main topic: how do you format your tables in this beautiful way? Cheers!
Thank you Silvio. I use a combination of the Minimal Theme + Minimal Theme Settings, Style Settings Plugins and Custom CSS Snippets for Tables. Only use CSS for my LifeOS but the rest of the vault uses the Minimal Theme :)
i just notice but how did you make the link in yaml turn into actual link when in reading mode? coz mine don't even when i type it in like you did in the video
Hi Jake. If you wrap your link in quotes it should show in reading mode. Topic: “[[Obsidian]]” set the property type to list if multiples
@@PaulDickson7 yeah i tried that as well but idk why it not working my obsidian tbh
Instead of adding the Link in Source Mode, see if you can add it in the Live Preview. Inside the Property Field, start typing [[ then the name of the note you want to link to. Choose the note and Obsidian with auto format the YAML for you. Make sure the note you're linking to exists. Do you show your properties in your Note?
@@PaulDickson7 thank you it work in live preview, still don't get why it don't work in source mode but i atleast i find a way to do it now
Source mode can be very picky with spaces :)
This looks cool but I don't have the properties you have, how can I have those? Should I delete types.json or how can I make it generate a new one or a correct one? The properties I see are:
aliases
link
links
tags
cssclasses
excalidraw-autoexport
excalidraw-border-color
excalidraw-css
excalidraw-default-mode
excalidraw-embeddable-theme
excalidraw-export-dark
excalidraw-export-embed-scene
excalidraw-export-padding
excalidraw-export-pngscale
excalidraw-export-transparent
excalidraw-font
excalidraw-font-color
excalidraw-link-brackets
excalidraw-link-prefix
excalidraw-linkbutton-opacity
excalidraw-mask
excalidraw-onload-script
excalidraw-open-md
excalidraw-plugin
excalidraw-url-prefix
Ok after few hours of banging my head I think I solved:
- Removed all properties from all notes (not many as the vault is new)
- Unassigned all that I'm allowed to, remains aliases, cssclasses and tags
- Now the types.json is finally very empty and clean
- I am able to add new properties from the code view
Hi Riccard, anything with prefix excalidraw is related to the Excalidraw plugin. YAML Properties are added to Markdown Notes (.md files)
Happy you were able to work it out but still a little confused why you're making changes to .json file
Doc - help.obsidian.md/Editing+and+formatting/Properties