removed emoji from filenames, Obsidian changed all relevant links

Corpus/Sparks/Using Obsidian 2.md

@@ -0,0 +1,21 @@
+The choice between frontmatter and main text for internal links in Obsidian depends on the purpose and nature of the links:
+
+**Put links in frontmatter when:**
+
+- Creating structured metadata relationships (like tags, categories, or formal associations)
+- Building MOCs (Maps of Content) or index pages where you want clean, scannable link lists
+- Using plugins that specifically read frontmatter fields (like Dataview queries)
+- Creating "up" links to parent topics or broader categories
+- Setting up formal taxonomies or hierarchical relationships
+
+**Put links in main text when:**
+
+- The links are part of your natural writing flow and thinking process
+- You're making contextual connections that relate to specific ideas or sentences
+- The links represent your active thought process while writing
+- You want the links to be part of your reading experience when reviewing notes
+- The connections are discoveries or insights that emerged while writing
+
+**Hybrid approach:** Many Obsidian users combine both methods. For example, you might put formal category links in frontmatter (`parent: [[Project Management]]`) while keeping contextual, thought-based links in the body text where they naturally arise during writing.
+
+The main text approach tends to be more organic and supports the "thinking in writing" philosophy that many note-takers prefer, while frontmatter links are better for systematic organization and plugin automation. Consider your primary use case: if you're building a knowledge system for later querying and analysis, lean toward frontmatter structure. If you're thinking through ideas and making connections as you write, embed them naturally in your text.