shit_admin: 2026-08-13 12:41:21

2026-08-13 12:41:21 -04:00
parent f369d56026
commit ca7081dd92
162 changed files with 7552 additions and 4 deletions
@@ -0,0 +1,33 @@
+# Callouts reference
+
+## Folding and nesting
+
+~~~markdown
+> [!faq]- Collapsed by default
+> Hidden until expanded.
+
+> [!faq]+ Expanded by default
+> Visible but collapsible.
+
+> [!question] Outer
+> > [!note] Inner
+> > Nested content.
+~~~
+
+## Built-in types
+
+| Type | Aliases |
+| --- | --- |
+| note | — |
+| abstract | summary, tldr |
+| info | — |
+| todo | — |
+| tip | hint, important |
+| success | check, done |
+| question | help, faq |
+| warning | caution, attention |
+| failure | fail, missing |
+| danger | error |
+| bug | — |
+| example | — |
+| quote | cite |
@@ -0,0 +1,27 @@
+# Embeds reference
+
+~~~markdown
+![[Note Name]]
+![[Note Name#Heading]]
+![[Note Name#^block-id]]
+
+![[image.png]]
+![[image.png|640x480]]
+![[image.png|300]]
+
+![[audio.mp3]]
+![[video.mp4]]
+
+![[document.pdf]]
+![[document.pdf#page=3]]
+![[document.pdf#height=400]]
+~~~
+
+A list embed needs a block ID after the list. An embedded search uses an
+Obsidian query block:
+
+~~~~markdown
+~~~query
+tag:#project status:done
+~~~
+~~~~
@@ -0,0 +1,18 @@
+# Properties reference
+
+Properties are YAML frontmatter at the very start of a note.
+
+| Property type | Example |
+| --- | --- |
+| Text | <code>title: My title</code> |
+| Number | <code>rating: 4.5</code> |
+| Checkbox | <code>completed: true</code> |
+| Date | <code>date: 2026-07-21</code> |
+| Date and time | <code>due: 2026-07-21T14:30:00</code> |
+| List | <code>tags: [one, two]</code> or a YAML list |
+| Link | <code>related: "[[Other Note]]"</code> |
+
+Obsidian reserves <code>tags</code>, <code>aliases</code>, and
+<code>cssclasses</code> for their built-in behaviors. Tags may contain letters,
+numbers (not as the first character), underscores, hyphens, and forward slashes.
+Prefer YAML lists when a property naturally has multiple values.