Yes, tbh. But thinking in namespaces as one-dimensional hierarchy is too restrictive and limits organizing ability for me. I just can’t get used to it - the properties’ alternative feels like the most ideal way. It needs to get some more feature love though. I consciously did not suggest any graph visualizations here (of course theses would be very nice), as from my experience time-consuming to implement.
Instead harvest low-hanging fruits. Example: per-page default queries. These might provide a quick answer, how to visualize hierarchy/relations. Let’s stay with the boats - browsing for relations in link reference currently is cumbersome:
Instead we could define one or more default queries per-page by using :current-page (dynamic variable) and place it either at page header or foot above linked references or hiearchy (position customizable):
This probably is much easier to implement, as there already exist journal default queries. Just as an example, curious there are better ideas.
(This is above query, if interested)
#+BEGIN_QUERY
{
:query [
:find (pull ?b[*])
:in $ ?cp
:where
; these two lines are just to optimize performance
[?p :block/name ?cp]
[?b :block/refs ?p]
; the actual work - filter by link in :extends
[?p :block/original-name ?po]
[?b :block/properties ?props]
[(get ?props :extends) ?prop_extends]
[(contains? ?prop_extends ?po)]
]
:inputs [:current-page]
}
#+END_QUERY