As noted in #29, I make use of Logseq's built-in hierarchy functionality, where creating a page like [[Mr Color/GX/3 Red]] creates a new page nested underneath parent pages. In this case, [[Mr Color]], [[Mr Color/GX]], and finally [[Mr Color/GX/3 Red]]. If the parent pages do not exist,they are added to the graph automatically, analogous to mkdir -p mr-color/gx/3-red.
Additionally, the generated pages are aware of their hierarchies:
parents know about their children, and list them
children know their path, and list it
Parent:
(Grand) child:
Schrodinger already creates these pages, but they lose awareness of their hierarchy links. It would be useful for these to be surfaceable in a published site link backlinks. Unfortunately, because they are not links present in the content, they do not get generated, and would require new work to do so.
As noted in #29, I make use of Logseq's built-in hierarchy functionality, where creating a page like
[[Mr Color/GX/3 Red]]creates a new page nested underneath parent pages. In this case,[[Mr Color]],[[Mr Color/GX]], and finally[[Mr Color/GX/3 Red]]. If the parent pages do not exist,they are added to the graph automatically, analogous tomkdir -p mr-color/gx/3-red.Additionally, the generated pages are aware of their hierarchies:
Parent:
(Grand) child:
Schrodinger already creates these pages, but they lose awareness of their hierarchy links. It would be useful for these to be surfaceable in a published site link backlinks. Unfortunately, because they are not links present in the content, they do not get generated, and would require new work to do so.
Could these be added to page front matter? Maybe