# Collapsible Section in Rich Text

**URL:** <https://community.fibery.io/t/collapsible-section-in-rich-text/7539>\
**Category:** Ideas & Features\
**Tags:** rich-text\
**Created:** [October 11, 2024, 9:45pm UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539 "2024-10-11T21:45:22Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\
**Post date:** [October 11, 2024, 9:45pm UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/1 "2024-10-11T21:45:22Z")

</div>

Really enjoying exploring what’s possible in Rich Text with Fibery’s robust editor – embedded views is a game changer! However, one wish I keep coming back to is to have a section in our text areas that can be collapsed / expanded.

Obsidian has a nice implementation of this, I believe they call it “Folding” over there:

![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/3/3035162da2f4fb059ab058feb415f9f8cbb80666.png)

This would help create rich and robust documents within a single entity, as well as keep usability high by reducing visual clutter / noise.

---

<div class="post-metadata">

**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\
**Post date:** [October 12, 2024, 11:10am UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/2 "2024-10-12T11:10:44Z")

</div>

You got my vote! This would be extremely helpful. Notion also solves this in a good way.

We have a lot long documents, SOPs and content that we want to share in public via Fibery. Currently it looks really overwhelming because you can’t collapse sections.

(especially when you share it in public; then everything is auto expanded when you used headers)

---

<div class="post-metadata">

**Author:** ![grex22](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/grex22/32/10249_2.png) [@grex22](https://community.fibery.io/u/grex22)\
**Post date:** [October 12, 2024, 4:01pm UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/3 "2024-10-12T16:01:16Z")

</div>

Umm… Well, maybe the idea of distinct “boxed” sections is still a good one, but until your comment @YvetteLans I didn’t realize that headers in Fibery acted as collapsible sections!! This is great! 😁

I DO still think that having distinct “boxes” that are closed by default would be a nice addition, especially for long documents / SOPs.

---

<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:** [October 12, 2024, 6:42pm UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/4 "2024-10-12T18:42:09Z")

</div>

I find Notion’s (original) “toggle block” to be an annoying piece of garbage, personally. 😆 Mainly because it enforces a fairly unpleasant and not-very-useful text style. Fibery’s header toggle is better at least than that. Notion did eventually add Toggle Headers as well, but as in Fibery it’s still limited. So hey, if we’re asking for collapse/toggle sections, and since we have something of a concept of Blocks now, I’d ask for something more broadly interesting as far as layout is concerned (wish I had a version of this feature request in a more general place, but for now I don’t):

> **[Make "toggle" a feature of every block](https://community.anytype.io/t/make-toggle-a-feature-of-every-block/1001)**
>
> In Anytype and Notion, “toggle” is currently implemented as a type of list. This means I can only ever have the default text size for a toggle and it creates a needlessly limited use case. In other words, the utility of the collapse function is...

As far as how the toggle state is persisted, I think for now it should be remembered per-user. But a future admin option to set default toggle state would be cool.

---

<div class="post-metadata">

**Author:** ![YvetteLans](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/yvettelans/32/6101_2.png) [@YvetteLans](https://community.fibery.io/u/YvetteLans)\
**Post date:** [October 12, 2024, 7:26pm UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/5 "2024-10-12T19:26:53Z")

</div>

> [@Oshyan](#):
>
> Notion did eventually add Toggle Headers as well, but as in Fibery it’s still limited.

What I like about Notion’s set-up is that it’s really dummy proof that you can collapse/expand. And that you can color the blocks.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/fibery/original/2X/e/ee17a54f614a5f59ca68bbdc462799e58d0a9d0a.png)

Especially colors can create a big difference when you have large documents.

> [@Oshyan](#):
>
> As far as how the toggle state is persisted, I think for now it should be remembered per-user. But a future admin option to set default toggle state would be cool.

When you share a document in public, I think setting a default toggle state is a must have. If everything is expanded, it will create overwhelm.

I’ve read your feature request. But I’m not getting it fully 😅

What would be the benefit of a block? That you can easily drag & drop? Or do you also want to re-use blocks, link to blocks and other cool stuff?

---

<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:** [October 13, 2024, 12:55am UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/6 "2024-10-13T00:55:09Z")

</div>

> [@YvetteLans](#):
>
> What would be the benefit of a block? That you can easily drag & drop? Or do you also want to re-use blocks, link to blocks and other cool stuff?

In Notion and Anytype _everything_ is a “block”. Fibery hasn’t fully embraced this in the UI, much to my disappointment, but as you can see with the recent addition of “[Drag to Reorder Elements](https://community.fibery.io/t/rich-text-drag-to-move-reorder-elements/2960)”, most things in Fibery are “blocks” too! So why not have a toggle on _every_ block? No, not one that is visible all the time, just on-hover, like the Block Handles in Notion. Maybe it becomes “sticky” visible in collapsed state. So you could toggle any Heading, sure, but also a **any level of a bullet list** ([a separate feature request in itself](https://community.fibery.io/t/a-few-should-be-easy-rich-text-features-to-add-from-remirror-hr-mixed-lists-collapse-lists/3663)), or an in-line Table, or a code block, or an embed. _Anything_ that is taking up too much space. The point of it is basically this: most often I see people putting things they want to collapse “inside” of toggle-able blocks. But, for example, often I did not _want_ a header or toggle there, I just wanted to collapse some embed(s) or something. But I _had_ to make a toggle block in order to collapse what I _actually_ wanted to collapse. Toggle on all blocks solves this elegantly IMHO.

This would probably require Fibery more deeply embrace “blockness” to really work well though.

> [@YvetteLans](#):
>
> What would be the benefit of a block? That you can easily drag & drop? Or do you also want to re-use blocks, link to blocks and other cool stuff?

All this would be great one day, though I have doubts it will happen any time soon, if ever. But since Fibery is _already_ able to address many discreet pieces of Rich Text as “blocks”, why not make them all toggleable at least? Doing so does not require all the other fancier features of blocks.

---

<div class="post-metadata">

**Author:** ![CivicScribe88](https://avatars.discourse-cdn.com/v4/letter/c/5f9b8f/32.png) [@CivicScribe88](https://community.fibery.io/u/CivicScribe88)\
**Post date:** [October 13, 2024, 6:40am UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/7 "2024-10-13T06:40:46Z")

</div>

Fibery’s Headers are really a pain for me. I get how the levels work and I get how it provides a lot of useful functionality.

But I really wish there were just a collapsible block like in Notion. As Oshyan points out though, since Fibery isn’t built on blocks, I don’t see a good way around this. Maybe a Start block and an End block for collapsible sections? Right now I think headers work like that. Once a header is implemented I guess everything under it collapses into it - and that’s broken only be a new same-level-or-more-senior header underneath of it?

Sometimes I just want to write, and thinking about the hierarchy of headers is annoying.

---

<div class="post-metadata">

**Author:** ![Minh\_Tri\_Do\_Hang](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/minh_tri_do_hang/32/6791_2.png) [@Minh\_Tri\_Do\_Hang](https://community.fibery.io/u/Minh_Tri_Do_Hang)\
**Post date:** [October 14, 2024, 1:13am UTC](https://community.fibery.io/t/collapsible-section-in-rich-text/7539/8 "2024-10-14T01:13:35Z")

</div>

Folding 's really helpful in obsidian, when rich text can be a lot in 1 page  
I need to to collapse and expand by hot key for this
