[US-19] As a user, I want a block I've placed in one document (e.g., a task list) to stay live and in sync if it's also embedded in a different document or a chat, so I only maintain one copy of shared content. #9

Open
opened 2026-08-21 17:47:47 +02:00 by angie · 3 comments
Owner

@yousef maybe preliminary at this moment, but let's not underestimate the UX + engineering challenge of this

@yousef maybe preliminary at this moment, but let's not underestimate the UX + engineering challenge of this
Owner

This is the main dish of the whole ELFA proposal. We want embeddable blocks that stay in sync. Technically, NextGraph has been designed for that. The shell is ready for that too, as it can load mini-apps and components within other components. We will test how BlockNote or IronCalc can embed each other as well as other apps. That is the main goal of the whole thing.

This is the main dish of the whole ELFA proposal. We want embeddable blocks that stay in sync. Technically, NextGraph has been designed for that. The shell is ready for that too, as it can load mini-apps and components within other components. We will test how BlockNote or IronCalc can embed each other as well as other apps. That is the main goal of the whole thing.
Owner

Sure, I'm just pointing out some possible complexities that we should anticipate;

  • Embedding basic IronCalc documents within BlockNote won't be that difficult
  • Embedding BlockNote in IronCalc poses many UX questions, what should that look like
  • We'd need to make sure we respect (technically) and explain (UX) the permissions of the embedded document (e.g.: read/write/suggestion/comment access)
  • Complexities with embedding "single blocks";
    • In BlockNote, documents are stored as one Yjs document. We can load the entire document and distill the embedded blocks for it
    • Lists are not a unit in BlockNote at this moment (only list items)
    • How do we load / show the "history" of a document when it actually consists of multiple documents?
  • What UX patterns can we use for a document that embeds content from different documents to "still make sense"? How do we prevent users from editing a block in one document in a way it makes sense within the context of that document, but completely breaking the context in another document where the block is used? etc.

(no need to answer these now, it's just to paint a picture)

Sure we can figure out exciting ways to make this work, just saying we shouldn't underestimate the effort involved)

Sure, I'm just pointing out some possible complexities that we should anticipate; - Embedding basic IronCalc documents within BlockNote won't be that difficult - Embedding BlockNote in IronCalc poses many UX questions, what should that look like - We'd need to make sure we respect (technically) and explain (UX) the permissions of the embedded document (e.g.: read/write/suggestion/comment access) - Complexities with embedding "single blocks"; - In BlockNote, documents are stored as one Yjs document. We can load the entire document and distill the embedded blocks for it - Lists are not a unit in BlockNote at this moment (only list items) - How do we load / show the "history" of a document when it actually consists of multiple documents? - What UX patterns can we use for a document that embeds content from different documents to "still make sense"? How do we prevent users from editing a block in one document in a way it makes sense within the context of that document, but completely breaking the context in another document where the block is used? etc. (no need to answer these now, it's just to paint a picture) Sure we can figure out exciting ways to make this work, just saying we shouldn't underestimate the effort involved)
Owner

it is good to start the discussion on this topic:) thanks for the input.

it is good to start the discussion on this topic:) thanks for the input.
Sign in to join this conversation.
No milestone
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ELFA/rfd#9
No description provided.