> so having an ID for each block will make the plaintext look out of place (say, if you wanna move your files to another app). Indeed, this is definitely a pro

> so having an ID for each block will make the plaintext look out of place (say, if you wanna move your files to another app). Indeed, this is definitely a problem for Logseq. For example here's some of my recent Logseq notes. This is one page where you can see an "ID" (represented by `id:: <guid>` is created. Then helpful images/diagrams are displayed. This is then referenced later: - Parts of a [[Neuron]] id:: 64f4bdc3-29de-4b6c-bc41-20a5f052badf - Dendrite: https://en.m.wikipedia.org/wiki/Dendrite - {:height 411, :width 718} - Axon: https://en.m.wikipedia.org/wiki/Axon - {:height 471, :width 718} Then in a different page, this is referenced by ID. In this case it is "embedded" but you can also reference and other possibilitie: - #vocabulary [[Brain Myths Exploded]] #Notes - {{embed ((64f4bdc3-29de-4b6c-bc41-20a5f052badf))}} - Encephalization Quotient (not a good measurement)