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:
This would help create rich and robust documents within a single entity, as well as keep usability high by reducing visual clutter / noise.
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)
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.
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):
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.
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.
Especially colors can create a big difference when you have large documents.
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?
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”, 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), 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.
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.
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.
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