# Insigths new editor and data structure. ### Problem - The current **editor engine** is a **"black box"** that's hard to make complex customizations. - The format we **store** Insights content **data** it's not extensible, scalable and it's **hard to manipulate**. ```mermaid graph LR A((Insighs web))-->|HTML|B[(DB)] B -->|HTML|A ``` ### Solution 1. Implement the editor with a **new engine** called **Quill**. 2. Migrate the current Insight's **content data** to the **Quill Delta** data structure, that was designed for this porpuse. ```mermaid graph LR A((Insighs web))-->|HTML|B(Quill editor) B-->|Delta|C[(DB)] C -->|Delta|B B -->|HTML|A ``` ### Benefits - More control over our editor, **unlocking** the development of **complex interacions** such as **Zettelkasten** and more. - More power over our **data**, falicitating the future **machine learning** and **AI** interations. - Reimplement **editor** with more context, making it neater, more robust and **competitive**. - Makes it **much easier** to build an Insighst **mobile app** with editing capabilities. ### Cost About **two weeks** worth of development.