I’m happy that blocks are being implemented in doc views, they are a must. However, the rich text editing I think needs a bit more improvements, as it’s not as smooth as I wanted to be. Most of these are just small things and might be subjective, but it’s something I would like: Major one - allow indentation when pressing tab for any element. I hate that I can’t indent normal text or checkboxes. Here’s how coda does it Hiring · test | Loom [FIXED - BUG] - when you’re on a checkbox item and press enter, it creates a new empty checkbox. However, sometimes the next time you press enter, either creates another empty checkbox (not desired) either removes the checkbox to add a new normal, non-checkbox item. Creating empty checkbox items is not desired and not consistent. Here’s an ex. New document | Fibery | Loom [DONE] Allow text color change, not just highlights. [FIXED] Maybe just a personal preference, but heading should be much more distinguishable from normal text. H3 is barely distinguishable, makes thinks harder to read. Maybe increase the size a bit of all headers and bold them. The bottom margin of the headers should be a bit larger, makes things easier to read. Collapsible icon can be just a tiny bit bigger and have some hover action, feels a bit better when i see in Coda that highlights the arrow when i hover over it. I also like the arrow animation when I click on it. [DONE] Icon picker for left sidebar items :slight_smile: I know we can simply copy-paste an icon from the web and put it on the beginning of the view name, but would be much better to simply let us pick an icon. You already have the icon picker so… To be completely honest, I tend to go to Coda for building documents to share with the team, they look cleaner (bigger bolder headers just an example) and are easier to edit. We really want to ditch Coda to not keep things in multiple places, but there are little things like that that keeps us going back to them.

That sounds a bit intense to implement and maintain, if I’m not mistaken. Do you really need per-type CSS customization?

Another big one I remembered today while a wrote features spec is the sub-items numbering. If we have numbered items, sub-items are also numbers. It’s more natural to have letters there. Another thing is that I can’t change the sub-item to be just simple non-ordered/ non-numbered items… they are always numbers. I might want to be checkboxes or normal items. [Later edit] Following up on last matter, would be super nice if on sub-items when we type “1.” to change the sub-items to numbering, when we type “” to checkboxes and * to normal items …basically like it works when we’re not editing under an item. To be completely honest, if they just straight up copy the full document editing behaviour from Coda it would be superb.

My thought was to just convert Type IDs and entity IDs to class names, and add to the appropriate HTML elements - seems like that should be pretty easy to implement.

Hmm OK. I’m honestly not sure, so you may be right.

And these don’t actually need to be CSS classes – they could just as effectively be custom HTML attributes, as long as we can create selectors to match and style them. Maybe something like: fibery-typeid="..." and fibery-entityid="..."

I am now upvoting this largely because of the first request, for indenting. I especially want this for checkboxes. If this should be its own feature request to vote on, then fair enough.

Any progress here? 6 months passed and none of the issues we listed here were addressed. The document experience is pretty poor even after so long time… No checkbox indentation, checkboxes bug still present, you can’t combine ordered lists with non-ordered sub-lists or checkboxes and vice-versa, can’t use other type of order style like letters or greek letters, h3 looks almost the same as normal text and so on.

Hold on, we will get to it soon!

We could cut down on some of the forum chatter if there were links in the topics here to where we could track an issue’s status and ETA. :bulb:

baby steps… WIP [2022-05-20 14.52.33]

Some more love on document editing

Ideas & Features

Ilovefibery February 9, 2026, 1:41pm 23

Topic		Replies	Views
We've improved Docs greatly this year. Do you still REALLY miss something? News & Announcements	48	3743	January 26, 2024
Ability to tab indent / indentation in rich text and document Ideas & Features	0	33	February 9, 2026
Natively integrated custom CSS (and editor) for Fibery workspaces Ideas & Features	29	1718	July 30, 2026
[DONE] Table view Description field / Rich Edit fields in Table View Ideas & Features table-view	27	3922	July 4, 2024
[DONE] Allow pasting markdown in rich text field Ideas & Features rich-text	9	715	March 19, 2026

Some more love on document editing

Related topics