I think a reference format based on block-names rather than UUID could unlock a host of other natural features in Logseq.
Right now, as far as I know, you can’t :
- add a block to the favorites sidebar
- display blocks on the graph
- insert a page’s content as seamlessly as a block reference does
In other words, at the moment “everything is a block in Logseq” except pages, which are more much central than blocks but are also less flexible in other respects.
The way I see it, a [[page-name#block-name]] format would make it easier to integrate in favorites and graph, as well as any other features where pages refs show up but block refs don’t. Inter-operability with other markdown editors is a welcomed bonus.
Extending that idea the other way around, you could also have a ((page-name)) reference format that inserts the (editable) contents of the pages seamlessly in the document you’re working on.
This to me is an important step towards making references as easy as possible. As @and_yet_it_moves mentioned, page vs block is mostly a file system distinction & there’s no reason to force our thinking to adhere to it, rather it should be the opposite.