You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Could a secondary sidebar be populated with first/second/third level headings in a collapsible tree-like fashion, and navigate to those headings in the browser panel when clicked? Bonus points if the highlighted heading in the sidebar also synchronizes with the current position in the browser (even collapsing when leaving that nested level?).
Of course this is fairly complex logic, which is why it isn't even implemented in most full-fledged documentation themes, so it might be a tall order! The PyData Sphinx theme does it, for example.
The text was updated successfully, but these errors were encountered:
Sorry, I was too broad in the scope of my request.
The "missing" feature here (relative to the PyData example) is just in a two-way sync where the sidebar highlight tracks along with your reading progress in the document, acting as a sort of "you are here" feature.
A secondary feature, a design choice in the PyData theme, is to also have the sidebar contents by default just show first-level headings, but expand to show deeper headings as you scroll through, and collapse as you leave a given "chapter" or section. These are frills on top of the table of contents, but I find it convenient for locating oneself, especially in longer documents.
That makes more sense, thanks. I don't think our Markdown widget has a convenient method of tracking that right now, but I'll keep it in mind (this might end up being rolled into a Textual issue).
Could a secondary sidebar be populated with first/second/third level headings in a collapsible tree-like fashion, and navigate to those headings in the browser panel when clicked? Bonus points if the highlighted heading in the sidebar also synchronizes with the current position in the browser (even collapsing when leaving that nested level?).
Of course this is fairly complex logic, which is why it isn't even implemented in most full-fledged documentation themes, so it might be a tall order! The PyData Sphinx theme does it, for example.
The text was updated successfully, but these errors were encountered: