My approach to [[Obsidian]] is to utilize as few plug-ins as possible. This is because [[Simple is Maintainable]] and any special syntax enforced by a plug-in (like the [[Dataview Plug-in]]) will make [[My Notes]] _less_ portable and _more_ tightly [[Coupling|coupled]] to Obsidian and those plugins. This means I'm losing some of the potential [[Obsidian Niceties]], but doing so willingly. This is an example of [[Choose Your Own Trade-Offs]], maximizing [[System Fault Tolerance]] at the expense of some functions. I decided to [[Make the Decision that Informs all Subsequent Decisions]]: > [!tip] I will defend the portability of my notes through the commitment to plaintext & durable, open file standards. This does **not** mean "use no plugins". This means the plaintext [[Principles I Like|principle]] I'm following needs to be considered. All the plugins I build will defend note portability (i.e. not make them less portable). Similarly, I will [[Format These Notes to Work in Plaintext]]. # Specific Examples - I no longer use the [[Dataview Plug-in]] in my vaults. - I use the [[Excalidraw]] plugin in a very specific way - see [[Excalidraw in Obsidian]] for details - I will use the [[Obsidian Linting]] "Linting" plugin to _enhance_ portability. ## Exception - [[Obsidian Bases]] are sweet. I'm using those - but trying to do so in a capacity that *not* having them doesn't render my system broken. [[My Obsidian-Based Project Management System]] uses them, but doesn't *rely* on them to make tasks visible, for example. **** ## Source ## Related - [[Obsidian Linting]]