# The Automatic Table of Contents is often useless **URL:** \ **Category:** Bugs & Issues\ **Created:** [September 12, 2023, 8:05pm UTC](https://community.fibery.io/t/the-automatic-table-of-contents-is-often-useless/5136 "2023-09-12T20:05:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [September 12, 2023, 8:05pm UTC](https://community.fibery.io/t/the-automatic-table-of-contents-is-often-useless/5136/1 "2023-09-12T20:05:36Z")
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’. ![fibery table of contents issue](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/75da90f9a04b92088d8328cbd3ef9663a33b0288.png) ---
**Author:** ![Oshyan](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/oshyan/32/11431_2.png) [@Oshyan](https://community.fibery.io/u/Oshyan)\ **Post date:** [September 12, 2023, 9:45pm UTC](https://community.fibery.io/t/the-automatic-table-of-contents-is-often-useless/5136/2 "2023-09-12T21:45:44Z")
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](https://community.fibery.io/t/done-table-of-contents-block-or-other-function/2235): > > 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](https://community.fibery.io/t/in-dev-migrate-entity-view-to-blocks/2005) paradigm. Personally, though, I’d love to see it as something that can optionally “float” or exist outside/alongside the ma… ---
**Author:** ![Matt\_Blais](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/matt_blais/32/1464_2.png) [@Matt\_Blais](https://community.fibery.io/u/Matt_Blais)\ **Post date:** [September 14, 2023, 7:45pm UTC](https://community.fibery.io/t/the-automatic-table-of-contents-is-often-useless/5136/3 "2023-09-14T19:45:58Z")
**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. ---
**Author:** ![cannibalflea](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/cannibalflea/32/318_2.png) [@cannibalflea](https://community.fibery.io/u/cannibalflea)\ **Post date:** [September 16, 2023, 1:26am UTC](https://community.fibery.io/t/the-automatic-table-of-contents-is-often-useless/5136/4 "2023-09-16T01:26:10Z")
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: ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/f/ffc2621790fa433c8b4c21188adbc7d3588a6099.png) ---
**Author:** ![Yuri\_BC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yuri_bc/32/8803_2.png) [@Yuri\_BC](https://community.fibery.io/u/Yuri_BC)\ **Post date:** [March 23, 2024, 6:24pm UTC](https://community.fibery.io/t/the-automatic-table-of-contents-is-often-useless/5136/5 "2024-03-23T18:24:52Z")
Related workaround > [@Table of Contents (TOC) with anchor links](https://community.fibery.io/t/table-of-contents-toc-with-anchor-links/6011): > > 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…