So, i made a list of “Fiscal Hosts on Open Collective Relevant to Drupal Camps” and was putting it into Logseq.
Realized i would want this topic to be linked to from the Open Collective page.
Making the page title Fiscal Hosts on [[Open Collective]] Relevant to Drupal Camps was obviously goofy, and while the link to Open Collective worked there was no corresponding Linked Reference back to my new page.
This seems to affirm the general sense of those working in Logseq to prefer blocks over pages.
Which to me, to reduce mental overhead, means everything goes in the daily journal. (And perhaps later this block and its children moved into one of the topics it references?)
This still doesn’t feel right for me. Especially when i have a clear topic (albeit a compound one).
But creating a page with a compound topic really does not seem to work in Logseq. “Concept C applied to Organization O” should be the title, and it should show up in the references to both the Concept C page and the Organization O page with all of text written which is why having the first block of the page be something duplicative like “This is about applying [[Concept C]] to [[Organization O]]”, because the next blocks would have to be indented below that to all show up in the linked references as normal.
So unless there is some sort of page metadata that can declare what it should be linked to, multipart topics, where the title of the topic itself should link to one or more pages, need to be done as blocks.
And preslavrachev has a good point that although the Create Page dialog will show matching blocks as well as matching pages when you type in a title, trying to reference something from within a note means knowing if it is a page or a block first.
This part could probably be resolved satisfactorily with a feature request to have [[Starting to type a title]]
also show matches for blocks below and swap the whole [[
business out for ((
if you choose a block rather than a page.