@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.
I’d like to use Obsidian to do more longform writing inside the same system as my existing outline-based notes, but have a similar worry that my structure will be flattened when I return to my outline in Logseq.
Would a community plugin that told Logseq to parse Markdown heading levels (#, ## etc) as levels of an outliner hierarchy solve this problem? I guess you’d also have to work out how to tell it to deal with plain text blocks in between hierarchy levels (maybe always as children of the most recent header?).
Does a plugin like that exist, and if not how hard would it be to make one?