I've waffled on how to _format_ these notes. I'm settling on some [[Obsidian Linting]] rules that enforce formats that **work well in "source" ([[Plain Text Durability|plaintext]]) mode**. This is being done mostly because I wanted some simple [[Design vs Engineering|design]] principle that's simply stated that [[Make the Decision that Informs all Subsequent Decisions|informs]] the approach. It also defeats the portability of these notes and makes them inconsistent, which would make them more difficult to move to another service if I ever needed to. > [!tip] > The [Linter](obsidian://show-plugin?id=obsidian-linter) plugin for [[Obsidian]] is great for this! # Example Formatting Rules I'm Using - **Blank Lines** - Inserted before & after all headings - Inserted between paragraphs - Including separating bulleted lists from surrounding text - Including code fence blocks - Horizontal rules (`---`) may function as blank lines - Use correct [[Markdown]] heading levels, starting at `<h1>` - I used to start from `<h2>` headings sometimes, `<h1>` others - [[Obsidian Callouts]] are okay, they more or less work in plaintext **** # More ## Source - self ## Related