Content
View differences
Updated by Oleksii Borysenko about 20 hours ago
**As** a product owner \[enter role of user\]
**I want to** check the complexity of switching to BlockNote editor \[enter objective\]
**so that** I can understand how much time it may take and which risks we have \[enter desired result\]
**Acceptance criteria**
* provide a list of sub features with estimated time, complexity and risk for each feature
* after the analysis is done, we should be able to estimate the total effort needed to make BlockNote a switchable alternative to the Quill editor everywhere rich text appears (not just the workpackage description) with full macro parity, images/attachments, and markdown as the data format. <br>
**Technical notes**
* Package-based architecture. Editors become separate packages behind one editor-agnostic contract (op\_editor): `op_blocknote_editor` , <br>
**Permissions and — later — extract today's Quill into op\_quill\_editor. App-specific concerns (navigation, attachment upload, macro resolution) are injected as ports, so the packages stay standalone.
visibility considerations**
* Hosting = file:// (single bundled `Vite` build, offline). most likely not a localhost/remote server. **Still an open question.** _To whom is this feature visible?_
* Keep Quill. BlockNote _When is the alternative, it not a replacement (for now)
visible?_
**Translation considerations**
* Theme _Key terms and fonts parity: editor follows phrases in the app's light/dark theme.
key languages_
**Out of scope**
* Macros - port Quill embed builders <br>
_Set the_ **To be informed/consulted teams** _field to custom BlockNote blocks/inline specs + navigation.
* for images and attachments — upload handler + authenticated-image loading.
* (**TO BE DISCUSSED**) Read-only mode for long comment/activity lists - native render vs hybrid vs a recycled pool include all teams necessary to be informed of ~5–6 webviews the changes._
**I want to** check the complexity of switching to BlockNote editor
**so that** I can understand how much time it may take and which risks we have
**Acceptance criteria**
* provide a list of sub features with estimated time, complexity and risk for each feature
* after the analysis is done, we should be able to estimate the total effort needed to make BlockNote a switchable alternative to the Quill editor everywhere rich text appears (not just the workpackage description) with full macro parity, images/attachments, and markdown as the data format.
**Technical notes**
* Package-based architecture. Editors become separate packages behind one editor-agnostic contract (op\_editor): `op_blocknote_editor` ,
**Permissions
* Keep Quill. BlockNote
**Translation considerations**
**Out of scope**
_Set the_ **To be informed/consulted teams** _field
* for images and attachments — upload handler + authenticated-image loading.
* (**TO BE DISCUSSED**) Read-only mode for long comment/activity lists - native render vs hybrid vs a recycled pool