Table of contents for long/nested Lepiter documents?

[offray]

This is my latest data exploration data story powered by Pharo/Lepiter about how to migrate from Wordpress to TiddlyWiki. And here is a screenshot of our documentation workflow (we're adapting Lepiter while writing in it with new functionality/UI to support our documentation workflows):

In our data storytelling workflow, by clicking on (1) we launch a live preview of the document we are writing outside the image, exported in Markdeep running in a local server (2), so we can enrich the document with markup that is mostly compatible with Markdown, but give us advantages that "standard" Markdown (ie: CommonMark) doesn't have. I try to keep a single data narrative as the one in [a] in a single Lepiter document, to improve exportation and proofreading, but they can become long/nested data narratives. I would like to implement a table of contents like the one that is automatically shown on (3), by adding a new button to the Lepiter page on (4). So, by clicking on the (sub)section I can jump to that part of the Lepiter page. Does Lepiter support jumping to a particular part of documents and, If I want to create a table of contents for the current page (sub)titles, where I should start to look? I know that I can query LePage children and select all those which are (sub)sections, but I wonder if there is something premade or planned and about the functionality to jump to a particular LeSnippet.

[seandenigris]

"Last" as in "there will be no more" or "latest" as in "a point in a series"

[offray]

Thanks. Corrected. And the document is updated too. As you can see there, there is some discussion about licensing, that resonate with the brief talk we had about this topic in our virtual meeting.

I'll post my advances in my table of contents exploration in this thread.

[seandenigris]

I think my request on Discord is somewhat related to your TOC idea:

I think it would help navigability if header snippets:
had their content snippets as children
Appeared in the sidebar (automatically?)

But that suggestion was flatly rejected. My followup, which was unanswered was:

Interesting. It seems obvious to me. DB->page->section are finer meaningful subsections that one may or may not be interested in a particular context. Hence the value of jumping to and collapsing

IIUC there is no built in way to jump to a snippet, but similar behavior was implemented for individual methods in Coder, so it seems doable.

[offray]

I will try to have two table of contents. One for the documents, and other for the particular table of contents of each document. The Coder jump seems like a good idea to jump inside a document. I'll have to look at it and will report back here.

In general outlining is pretty weak in GT compared with alternatives like OrgMode, Leo Editor, particularly in two fronts:

• indexation: the ability to swiftly create outlines with several levels or hierarchy and break a complex document in such levels.
• navigation: the possibility to jump to the outlined levels.