🔮 ROADMAP (Features we are working on or will work on soon) UPDATED: 27 April 2022

[mdubakov]

This top-level post is updated on a weekly basis (approximately).

We-re slowly switching to this Roadmap in Fibery, consider it as a more up to date . | Fibery

NOW: Working on

[IN DEV] Please add Dark Theme

Would love the ability to have an all dark theme. Personally, I find it to be much easier on the eyes.

[IN DEV] Share Space to the web

Spaces can be shared to the web (set as Public), it means they will be accessible by anyone and indexed (or not) by Google. How to share space Admin or Creator can Share space to the web. This space becomes available to anyone . For example, If I have xxx.fibery.io Workspace and make User Guide space Public, then ANY anon visitor will see this Space in left menu when open xxx.fibery.io. Direct link to the space will be xxx.fibery.io/@public/user_guide Under the hood we use read-only users me…

[IN DEV] Add ability to fully edit fields after creation

One thing I’m finding increasingly frustrating is the inability to edit most aspects of Fields after they’re created. Notion seems to be able to handle this much better, even allowing you to convert between field types (e.g. text vs. multi-select) and maintain some of the data. Another common challenge I run into with this is not being able to set the Default Value after creating the Field. Sometimes I realize later that I want a default value, or sometimes I decide to change it after using it …

[IN DEV] Send emails from Fibery

Fibery should be able to send emails from connected Email Account. For example, I may connect my Gmail account and send emails directly from Fibery. It may be handy to send emails to leads and customers, etc. Create a list of leads, filter it as you wish, create an Action Button with Send Email action, select several leads and send the email. [image]

[IN DEV] Migrate Entity View to Blocks

We create a new Entity View where per-Type elements (rich-text Fields → Text Blocks, context Lists → View Blocks, etc.) coexist with per-Entity elements (Text/Whiteboard/View Block). Structured Fields (currently on the right) are left intact for now. No need to migrate EVERYTHING on the left (Files, Comments, etc.), these things are enough for the first iteration: Text Block (aka collabdoc, Prose Mirror) Permissions for native Blocks are a must. Contributors+ can reorder/add/remove Blocks on …

[IN DEV] Embed Custom Views into Entity View

This has been mentioned several times in various posts and requests, but never really seemed to have its own clear feature request, and I think it’s important: We need the ability to embed arbitrary Views into Rich Text fields anywhere (including Documents). Notion is really the best existing example of this and for the most part it handles this very well. You can embed a view of a database (Type) and filter and sort it as you desire. You can change the view type, card, calendar, list, gallery.…

Important Fields

We’ll see how it goes on live data — so far it’s a radical experiment. Correct, we imagine Creators marking some Fields as important which pins them throughout Fibery. This might include the creation screen as well, similar to Linear: [image]

NEXT: Consider for near future (1-2 months)

Individual Layouts for a node, hide fields etc

This may be some work … Currently the displayed layout of a Model shows all items. One good thing is, you can sort the fields. But you can not hide any. Seeing “creation date” and other fields for example is most times useless and overloads the page. BUT it is not a good idea to make it globaly for all views of a model anytime. It should be a way to have different layouts. Not sure what could be a good logic. Maybe it may depending on where you opened it? In any case a toggle for “show all f…

[PLANNED] Entity-level permissions

Why? So far all the access management in Fibery happens on the App level. The only way to share an individual Entity (ex. a Task) with a teammate is via read-only external sharing [image] Introducing Entity-level permissions will unlock new opportunities: Collaborating with clients As we’ve learned, Fibery is a surprisingly good fit for many service companies: think digital agencies and development studios. A good fit, that is to say, before we start talking about access management…

[APPROVED] Attachments in the document

Today it is not possible to add attachments in the document. We have to upload files to the Google Drive and then link them in the text.

[Haslien]

SUPER excited for all the stuff being added to In-dev this week! I see a lot of things I definitely would have use for, made my Monday a lot better

[Oshyan]

Yeah, 100% agree! I was reading down the list and got more and more hyped about the near future of Fibery.

[helloitse]

Love seeing the progress y’all are making here. Keep up the great work!

[Oshyan]

By the way, for anyone who wants to see what was added recently to the main topic up there you can click the little icon on the upper-right:

to see the change comparison view, then and just scroll down and look for stuff highlighted in green.

[Pagandai_V_Pannir_Se]

very good progress

[bear]

Great list!

Particularly, entry level permissions would be very useful to me!

Keep up the good work!

[webinit]

Do you have Fibery Forms on the roadmap at all?

[mdubakov]

We do, but we will not do it in the next 3-4 months, and we don’t plan further horizons

[Pagandai_V_Pannirsel]

Thanks , wish great grren future for the small creative fibery team , very big sucess next year after pandemic world economic crysis

[Julian_Dumitrascu]

1. Where is the Fibery database with Fibery features and their statuses?
2. Where have you described the communication features of Fibery?

[Chr1sG]

1. What exactly do you mean? This topic is itself a list of the upcoming features and their status.
   Did you mean that you wanted to see a full list of features, including those that have been done, those that are not yet on the roadmap, those that have been considered but rejected…

2. What do you mean by the ‘communication features’?
   Fibery has notifications (standard and customisable), it can integrate with Slack, it can sync with email (currently one-way). Is there something else you had in mind?

[Julian_Dumitrascu]

1. Yes.
   A database instead of a list.
   In Fibery instead of Discourse.
2. At least threaded conversations like in Reddit instead of the primitive “comment” field.
   I’d continue communicating with you at least about these things when I find more time.

[B_Sp]

@Julian_Dumitrascu

At least threaded conversations like in Reddit instead of the primitive “comment” field.

I am glad to get any support of improved comments, badly needed. For better or worse they are pretty “primitive” at the moment. I know it’s been said before, but it’s a glaring weakness in Fibery around so many other great features in the rest of the app…

[Julian_Dumitrascu]

I’ve liked Fibery since I discovered it: February 2021.
Glad to be in touch with you! I’ve linked to my Medium profile in my profile in this forum. Is this displayed to you?
I’m going to respond there to Michal.
I’m using many Discourse instances, but people can sell better when they communicate in the open. When you want us to buy from you or to recommend your services, discuss them on Medium! We discuss our services there.

[Jean]

I think he wants to see a public Fibery view with the features status instead of having them here like SaaS companies do with notion, using them as roadmap tool.

[mdubakov]

BTW, we will migrate to the new Roadmap that is synced with Fibery. Here is the preview:

https://the.fibery.io/@public/Public_Roadmap/Roadmap-Board-5974?app-sharing&enable-views-service

[cover]

cool stuff, thanks!!!

[webinit]

No forms on the current roadmap. Is this still something you’re looking to add in the future?