Place hierarchy above backlinks

[dippa-1]

As I

• Cannot register on the forums! #5096
  I have to write it here.
  Having the hierarchy places below backlinks doesn't make sense to me.
  If I navigate around, I don't want to scroll all the way to the bottom all the time.
  Having it at above backlinks would be way better imo.

[meldarionqeusse]

Preferably keep hierarchy at the top of the page

[lef-est]

yes this with a user configurable option in config.edn to control the threshold for collapsing (the default could be 3) just as there exists an option for linked references.

[cannibalox]

this needs more thought : when you have a big hierarchy, this can take a lot of real estate, so with the currrent implementation, I probably do not want to scroll through the whole list before seeing my notes, for example :

• imo, the best short-term solution would be a shortcut / button to insta-scroll down to the relevant section from the page-title area (and a floating button to scroll back up top too) and a button to FOLD the hierarchy section (consistent with the way we can fold linked references or Pages tagged with sections)

in any case, hierarchy gui could be further improved with additional features like :

• quick collapse hierarchy (more like a tree ?)
• maybe a button that would summon a movable window containing the hierarchy ? (a window with resize/rollup/pin)
• maybe this could be more like a breadcrumb (single line rather than a list) : root > first level > second level ... where each > separator would unfold a dropdown list of available branches ? this would enable even very long hierarchies to fit in a single line at the top of a page
  

[EasonSpirit]

see in here, we can vote to it!
https://discuss.logseq.com/t/hierarchy-can-be-augmented-by-tree-structure-with-collapse-buttons/3282

[meldarionqeusse]

I would rather have a long list to scroll and if I want to hide it I just collapse the Hierarchy. Whenever I use hierarchy I just have 3 - 5 items.

[castellco]

I would find this feature very useful. It would make Logseq a perfect alternative to Dendron, which principal feature is its hierarchical way to organize notes.

[TimLamoureux]

I would also rather see the hierarchy above the Pages tagged with... and the Linked References. To me, when I use hierarchies, it is because I want to be able to see the connected child pages more than the backlinks. Also, I assume (this needs to be confirmed) that hierarchies use fewer resources to find and generate than tags and linked references which could help with page load speeds.

That being said, I understand that everyone may have different expectations of how the interface should be structured. Would a better approach be to have the order of those sections defined as a configuration element? The most user intuitive method would be through drag and drop of the sections but having it in the config.edn is still viable.

[bendyorke]

I think this is something we could make 'theme-able'. If we do a little work, we could lay out the elements on the page in a single flex column. Then each section could be given a css order value on a case by case basis and you could sort them to your personal preference.

[filiptrplan]

Has anyone found a way to rearrange so that hierarchy is at least above the backlinks?

[chrispaynter]

I would find this helpful.

I want my linked references to be open most cases, however for my namespace pages, usually when I got to them (such as the root segment of the namespace), I am looking to see the overall heirachy, and the linked references is mostly noise in that situation.