Callouts are clunky…
And they seem to reenforce the webpage-proxy-cognitive frame (e.g. edit → preview → display | separating the inseparables of content from its context or creation from its usage), which limits development of broader, more robust, yet more essential/rudimentary tools for managing knowledge in Obsidian.
Seems we’re in search of a single, simple solution to multiple, complex problems/use cases.
It’s this kind of low-hanging fruit, the direct inverse of a “solution looking for a problem,” that precedes its “plucking.” Either via paradigm shift within a product or its corollary, market disruption without.
Or I suppose there’s the tragic third option for the fruit of frame-bound problem-solving: withering on the vine.
Forgive the nihilistic polemic. Must’ve poured too much Nietzsche in my morning coffee…