zadam / trilium

Build your personal knowledge base with Trilium Notes
GNU Affero General Public License v3.0
27.3k stars 1.91k forks source link

(Feature request) Collapsable Table of Contents #4564

Closed T-Trivium closed 6 months ago

T-Trivium commented 10 months ago

Describe feature

Hello,

First, I want to say thank you as Trilium has been fantastic, and continues to be the more I use it.

I would like to propose a small feature request. Is it possible to have an option to collapse certain sections within the table of contents viewer?

When there are large amounts of sections and sub-sections within a note, it could be helpful to collapse areas in order to focus on other sections.

Effectively, as an example, changing this:

trilex(1)

... to this (chapter 5 is fully collapsed): trilex2(1)

As a side note, I would like to keep all of the content together in a single note, rather than separating it out into the tree hierarchy of several notes.

Appreciate taking the time to see if this is at all feasible.

Thank you!

Additional Information

No response

meichthys commented 9 months ago

Sorry i don't have a perfect solution for you, but generally Trilium is not made for very long notes. It is usually better in Trilium to break notes down into smaller chunks and use the 'include' feature and/or rely on the card/list view at the bottom of the note to view sub-notes.

T-Trivium commented 9 months ago

Thanks @meichthys. Appreciate you taking the time to review this. I've tried using the 'include' feature and possible list format, but it is just a bit too clunky for me personally. Preference would be to have collapsible table of contents to be able to navigate easier. I've found #1850, which helps as far as navigating bulleted/checklist content, but doesn't fully help with navigating header information throughout a note. This feature would be nice, but I don't know how difficult it would be to implement it. Thanks.

meichthys commented 6 months ago

Trilium has entered maintenance mode. Future enhancements will be addressed in TrilumNext: https://github.com/TriliumNext/Notes/issues/77