The Automatic Table of Contents is often useless

[Yuri_BC]

Issue: long texts result in too many automatic TOC items
Suggestion: make the automatic TOC configurable to show only optional H1/H2/H3/H4’s PER ENTITY
I consider this ‘an issue’.

[Oshyan]

Agree. My original ToC feature request included this kind of thing as a desired feature, and I continue to think this and a couple of other things (like an option to “Pin” the ToC open per-page) would be good improvements:

[DONE] Table of Contents block or other function

I was surprised to not find an existing feature request for this one, but I did search a bit and only found brief mentions in otherwise unrelated discussions. So the request is simple: some kind of Table of Contents feature, for docs, certainly, but perhaps even just overall for Rich Text. Maybe even as a kind of Block in the upcoming [IN DEV] Migrate Entity View to Blocks paradigm. Personally, though, I’d love to see it as something that can optionally “float” or exist outside/alongside the ma…

[Matt_Blais]

Maybe add a “filter” UI to the top of TOC?
Type some text to filter the TOC (show the breadcrumb/path result of all matching headings), or select a Heading level to show only the headings at or above that level.

[cannibalflea]

I really like @Oshyan’s idea of TOC being a block and having some customizations like filtering.

One bug that seems to have recently appeared is that if you use an entity reference (using ‘#’) as a header, the entity name no longer appears in the TOC. There is an empty space which you can click on but the text does not appear:

[Yuri_BC]

Related workaround

Table of Contents (TOC) with anchor links

The script generates and appends a Table of Contents (TOC) for a rich text field (Description). It works by fetching the text, identifying headings and GUID anchor links to construct a TOC, and then updating the text with this TOC added at the beginning. In the gif I show two button automations, with and without ‘Callout’. [chrome_4vWWRtma7Z] Explanation Note: I chose to use JSON fetching and saving because directly manipulating the document content via JSON ensures that the existing GUIDs in…