I think the current asset system is difficult for users to understand because the terminology is somewhat inconsistent. In my opinion, the Logseq documentation should have described assets more appropriately as follows:
asset: A term referring to a special type of node in Logseq. Asset nodes are tagged with the existing built-in tag #Asset, which is hidden from users, so these nodes can be viewed on the #Asset page.
An asset contains two pieces of information: a name and a file. The part that can be freely edited in an asset node is the name. The actual file can be located by right-clicking the node and selecting Show File in Folder
Image and PDF files support built-in rendering, so the files themselves can be displayed directly within Logseq.
Therefore, an asset and an actual file are two different concepts. Linking to a file using  is simply a link to an internal file and has nothing to do with the asset system itself.
I think the current asset system is difficult for users to understand because the terminology is somewhat inconsistent. In my opinion, the Logseq documentation should have described assets more appropriately as follows:
asset: A term referring to a special type of node in Logseq. Asset nodes are tagged with the existing built-in tag
#Asset, which is hidden from users, so these nodes can be viewed on the#Assetpage.An asset contains two pieces of information: a name and a file. The part that can be freely edited in an asset node is the name. The actual file can be located by right-clicking the node and selecting
Show File in FolderImage and PDF files support built-in rendering, so the files themselves can be displayed directly within Logseq.
Therefore, an asset and an actual file are two different concepts. Linking to a file using
is simply a link to an internal file and has nothing to do with the asset system itself.