Thank you all for the really insightful and deep discussion. I’ll try to highlight our thoughts about View/Docs in Fibery and how it will fit together in the future. Note that this is not a plan yet, just intentions.
Initially, when we started design Fibery, we paid less attention to documents. We were focused on flexible domain and work management, but quite quickly discovered that documents are essential. Here we had two options:
- Implement usual text documents (like Google Doc)
- Go for Blocks approach (like Notion, Coda and new Wordpress)
Both approaches have benefits and problems. Documents In Fibery are part of Types in general, so we decided to go with usual text and implemented rich edit field based on ProseMirror.
Looking back I think this was a mistake, since blocks approach is more flexible and would give us more power in terms of Entity View composition.
Now we are thinking about Blocks addition into Entity View. Technically it should be possible to compose Entity View using any kind of Blocks (Table with related entities, Chart, native Fields, text, images, transclusions, etc). It means Block should be a first-class thing in Fibery. You may transclude or refer blocks, comment on blocks, have emoji for blocks, re-arrange them, etc.
There are many unknowns:
- How fast Entity View will operate if there will be 20-100 blocks?
- How it will affect Fibery complexity (conceptually)?
- How to make transclusions usable and useful?
- What will happen if people will add dozens of blocks with rich edit text?
- How to marry blocks with rich edit fields like Description? In fact there will be no Description field anymore, so how to handle this via API/integrations? Should we allow Named Blocks?
As you see, there are many conceptual and technical problems. I have a feeling that they are solvable.
I think it is very important and to be honest this is the last missing piece in Fibery to provide unmatched flexibility (well, + automatic rules, but they are in progress).
However, this project is a very challenging and will demand a team of 2-4 developers for ~4-6 months. So far we are working on things with more dense feedback (search, sharing, etc). But I do hope will get back to this problem in 2-3 months, so in the best case it will be delivered in the end of 2021.
Our sensing of the situation may change and we may start working on it sooner, but from what we hear this is not a top problem with Fibery adoption.