Outline Overview for sidebar

Displaying the contents of the top 2~3 layers of the doc tree in the sidebar would be an outline view that roughly meets most needs, I think.


This is a must have for me as well.

Maybe I’m missing something, but how do people that don’t want this feature navigate within large documents? I have documents with 50 “A4 pages” or more, and really have no feeling of where I am in the document or what else is in the document.

Having to add a “table of contents” manually feels super counter-intuitive and certainly does not work for large documents.

1 Like

Headers should be act as collapsible bulletpoints.
So the current rendering has some inconsistencies:

Subheader and Another h2 should be represented by a bulletpoint and be collapsible. So the markdown file above should be represented like this:


ps: If this is a bug, feel free to move it to its proper place or please tell me where to put this issue!

Absolutely agree. I’m trying to use LogSeq with Obsidian but the different handling/rendering of headers is making it difficult. If I don’t indent the bullet points in Obsidian then I can’t collapse the header in LogSeq. If I indent the bullets in LogSeq so the header is collapsible then it renders the bullets incorrectly in Obsidian (it seems to think they are code in this case).

Part of the problem is Obisidian treats anything with a tab indentation as a source block, there’s a fix you can make in logseq to change how indentation behaves by swapping it from tabs to number of spaces. Drop this into your config.edn, and then try creating a new document with indented bullet-points and you should see them render correctly in Obsidian.

 :export/bullet-indentation :two-spaces
1 Like

Thank you! I have been trying to figure out how to replace the indentation for a while!
This is not an issue with obsidian, as it is the default behavior for markdown standards.
4 spaces are used to define a codeblock

@tienson This FR has got many votes. Wonder if it’s on the roadmap.

1 Like

voted. like logseq, but I really want a outline/TOC, which is a must-have feature for a md editor, not to mention a wiki system.


I was about to suggest something similar. I’d love to see such a feature. All my pages have a certain structure at the macro level:

  • Models
    • Principles
    • Practical
    • Conceptual
    • etc
  • Questions
  • Learnings
    • Practical
    • Informational
    • Reflectional
  • Writings
    • Practical
    • Insights
    • etc.

I’d keep the outline of the page open in the sidebar at all times to quickly navigate it.

There’s a toc plugin here: GitHub - mschmidtkorth/logseq-msk-toc: A table of contents generator for Logseq

We just added support for plugins’ floating windows. @Charlie Should we make a PR on the logseq-msk-toc plugin?

1 Like

I think the possibility of collapsing all the blocks with a single click or a keyboard stroke would be a good solution, the document would become an outline of itself.


Glad to know there’s a plugin, will give it a try. Any chance it gets merged into the main repo?

1 Like

It could be! Would like to collect more feedback first.

1 Like

Having this ability in the right sidebar would be really convenient and useful


Chanced upon this FR. I’ve built a TOC plugin in the marketplace that can be opened in the right sidebar to facilitate easy navigation. Can take a look!



This is awesome!! I’ve been wanting a TOC/Outline view myself :smiley:

Maybe I am missing something. But in a large page, when you click outside the content and the CMD-UP a few time all blocks are folded till the main level, effectively the H1 level.
When I CMD-DOWN 1 time it opens the H1/H2 level.

And sometimes I even go further down but most of the time from this level I enter a Block by hitting the bullet and I can edit (also the sub-bullets for that H3 level).

And using the breadcrumbs at the top of the page I can quickly see where I am and navigate to a higher level … to deep dive in another place in the document.

So I guess an outline overview is already in the document.

1 Like

Generate a ToC from Namespaces!

Available Next Release :rocket::waxing_crescent_moon:

{{namespace [[Linux]]}}






Peek 2021-12-28 10-31


@Miro — the Zettlekasten method recommends zettles remain small. So one way to avoid the massive pages requiring a table of contents is to avoid massive pages. And one way to achieve some division in large bodies is to use the hierarchies feature. You could for example, write a book where every chapter existed as part of a hierarchy.

I’m not disagreeing with the feature request, I’m just offering suggestions for effectively dealing with it in its absence. When I find a page that’s oversized, I generally feel it needs split apart.

This TOC plugin allows a TOC in the sidebar.

The doc may be a bit confusing, but to use it in the sidebar showing the TOC for whatever page is selected:

  1. Install the plugin from the marketplace
  2. Open the “Contents” in the sidebar
  3. Added this line in the “Contents”: {{renderer :tocgen, *, 6, h}}