# \[DONE\] Table of Contents block or other function

**URL:** <https://community.fibery.io/t/done-table-of-contents-block-or-other-function/2235>\
**Category:** Ideas & Features\
**Tags:** blocks, rich-text\
**Created:** [November 20, 2021, 6:38pm UTC](https://community.fibery.io/t/done-table-of-contents-block-or-other-function/2235 "2021-11-20T18:38:26Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**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:** [November 21, 2022, 5:49pm UTC](https://community.fibery.io/t/done-table-of-contents-block-or-other-function/2235/13 "2022-11-21T17:49:25Z")

</div>

Now that I think about it, it’d be nice to be able to put a ToC block anywhere, but if that’s harder than a floating ToC, or the choice of dev resources comes down to _either_ a ToC block _or_ a floating ToC, but not both (for now at least), then I’d be in favor of a really good floating ToC design, collapsible, showing indentation for header levels, etc. It should show up in the “gutter” on the right or maybe left side of doc contents. Since it would be always available, it would largely address the desire to have ToC in a block, I think, and it could then be designed into the page settings, etc. This would also solve part of this recent FR:

> [@Better support for content editors to create a structured document](https://community.fibery.io/t/better-support-for-content-editors-to-create-a-structured-document/3573):
>
> Can we better support content creators structure a rich document? I’d like better support for content editors to create a structured document. Particularly, can we do something to help content creators apply the (correct) heading level (1-6)? When writing articles like wiki pages in Fibery, the structure is important, because: it helps with readability for users (headings) the only supported way to collapse content for users (headings) if you set the heading level wrong, collapse confuse us…

The Clover note-taking app has kind of a cool implementation of a subtle, persistent, collapsed, open-on-hover ToC. I’d prefer it to have the ability to “pin” it open though:  
 ![clover-toc](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/7/720de7c722b4fe2e8f415c2236d1b6aa8f0fa846.gif)  
Note how even in the collapsed state you can tell the header levels (H1-H3 are all that is supported) by the size of the dot. Subtle but clever.

---

_[View the full topic](https://community.fibery.io/t/done-table-of-contents-block-or-other-function/2235)._