‘Hierarchy Tool’ plugin

I have created ‘Hierarchy Tool’ plugin to enable hierarchical access.

  • Powerful tool for users who use hierarchy in Logseq.
    1. Follow the hierarchy of pages without having to open them
    2. split by header to provide a workflow for splitting a comprehensive page into sub-pages with increased information content.
    3. A table of contents facility optimised for displaying or splitting comprehensive pages where hierarchies or headers are used!

356910333-f2438a2a-019e-4e7a-bff1-b699a5ebabc3

My GitHub account is currently not published by GitHub and is inaccessible. This plugin is currently intended for versions prior to the Logseq db version.

Download here: https://firestorage.com/download/dd4017fa921eb58a4e6b248c33f12ffbb86593ad
Logseq developer mode only

  1. Toolbar [—] → Settings → Advanced → Developer mode (Toggle)
  2. Toolbar [—] → Plugins →Load unpacked plugin (Select the folder) *Unzip the .zip file and select the folder

That’s a nice one @YU000jp ! Thank you for sharing it.

It took me a while to go through the code (even a cursory look takes time for me). For anyone else reading, do not regard this as confirmation that it is safe to install. For one, the file may since have changed. But, most importantly, I am a terrible programmer. Please verify for yourself or trust someone else’s assessment.

I have tried it and I appreciate how it makes navigation within a long page and between pages of a namespace easier. It saves a lot of scrolling and page switching.
The ctrl+click shortcut to promote a block to a page saves time and removes a possible source for error or content loss. It’s very nice, and I wish there was a keyboard shortcut one could use in editing mode to trigger the same action.
I also enjoyed how easily I could reposition the sidebar, which was not immediately obvious to me.

You did not offer support nor ask for feedback, so feel free to disregard the following:

  • In using it, I am not sure I fully grasp what goes on within the section Page Connection. The namespace connection I think repeats the same as in >> of Tables of Contents with Sub-pages?

  • In the zip file there are two index.html one on the root folder and one under dist. I assume the one on the root folder is a remnant and may be removed. A version number may also help when you issue updates?

Glad to have your assessment. Logseq does not have a similar navigation to this plugin, so I tried to realise my possible idea. I want to change the search function of Logseq to a more powerful one.
A shortcut to promote a block to a page would be needed by many users. This shortcut will be improved so that it can also be used as a keyboard shortcut. (No immediate update)
‘Namespaces’ in “Page Connection” and “>>” in “Table of Contents with Sub-pages” are common. Each function can be hidden by folding it away, and the design allows users to use only the functions they want to use.

1 Like

That makes sense. Thank you for the explanation, and most importantly, for the time devoted to creating the plug-in and then sharing it. I look forward to any future updates, but it’s already super useful.

1 Like

That’s why two of the plugins you developed that I really enjoyed aren’t available from Logseq Marketplace anymore…
I ended up uninstalling all of my plugins during a cleanup and when trying to installing them again, your Github page and repositories were giving a 404 page and so I couldn’t install them through there anymore :,)

Was wondering what happened and now I know!

What’s the mechanism by which a block is turned into a page? Is it added as ParentPage/ChildPage with a block embed in the parent page?

One heading and its sub-blocks are converted into a page.

My GitHub account is now restored and users can download the plugin in the usual way.

2 Likes

Is it possible to ingest previously existing page hierarchy?

This tool is used to display the page hierarchy and headers at the same time.

These are excellent news!!