We’ve noticed that Fibery Creators (ourselves included) often put emojis at the start of View names. This way a View is easier to spot in the left menu and search. Also, relevant emojis are fun!
Now we make one step further — and introduce proper icons for Views. Pick between vibrant emojis and calmer icons and make your workspace shine.
This is part of a bigger theme of making Fibery more pleasant to use. We have always focused on raw power first, so now we are correcting for aesthetics and usability.
Speaking of pretty things, we’ve just introduced Formula formatting. Longer Formulas are no longer just lumps of text, but rather logically indented statements.
I love the view icons! I’ve already switched most of mine over lol. A nice related next step for me would being able to choose icons for databases. Then you could display a mini version for inline entities
To expand on this, it would also be nice if entities other than documents/views could have icons.
E.g. each Task or Project entity could have its own icon as well.
Yes this would be so nice! We’ve made an internal Wiki database in our customers workspaces because we have more flexibility with database entities then with documents.
We often link to Wiki entities. Would be so great if then also icons will show
+1
Currently we can’t wait until the new table grid is released since we can then clean up a lot of spaces. But in the meantime these releases makes us really, really happy
PS: I noticed that Pages (which were scrapped), had Page Descriptions, which the Documents do not have. Can we please get those for documents as well? I find myself adding a callout at the top of a document so often, which a small description would actually solve. Thanks!
Though the space between a squared emoji like and an M seems still a tad narrow to me… not only, but especially when compared to the default icons, the emoji still use a slightly different spacing.
But the former I know is nitpicking, the default icons I hope will be refined together with this
This is a great step forward, thanks! I was able to import all my chatgpt conversations which were stored as markdown files in folders with the date of the conversations. Fibery imported them as nested Fibery Docs.
Since we don’t use Fibery Docs, I need to convert them to our Page entity type. I have not found yet how to efficiently batch-convert this whole list (500 conversations in many date folders) keeping the structure, or even without the structure, as long as they are converted to an entity.
I think that entities need to have the first priority, not Fibery Docs in any app or feature that is assumed to be a generic solution like importing. Would you agree?