4 ms·
> I don't see how you could have a non "block" implementation? I mean, documentation is mostly text, image and code. You can easily be document-based instead o
by polote 5y ago
> I don't see how you could have a non "block" implementation?
I mean, documentation is mostly text, image and code. You can easily be document-based instead of block-based, like Confluence, Google docs ... you don't always need to be able to insert everything into everything.
I'm actually building a Confluence/Notion competitor, and it is document based. Being block-based makes a lot of things much more complex
- fellowniusmonk 5y agoInteresting, how do you handle line level or "intra-document" permissions then?
- polote 5y agoThe permission is at the document level. What are the use case of intra document level permission?
- emteycz 5y agoE.g. managers having different information about tasks diplayed in a table than programmers. You could do a different page for each group, but it's not as nice - different URLs, duplication of surrounding content, etc.
- polote 5y agoWell in my case each row is a document and the table is just a a specific king of structure, but is not embeddable in a document. But the thing is how generic you want your tool to be. In the notion case, everything is just an instance of something. So that's super flexible, but also super complex. You can simplify things by enforcing a structure while still doing 95% of the use cases You will never need to give a permission to a line of text