Content
View differences
Updated by Bruno Pagno 8 months ago
## Context
A custom version of commonmark combined with some HTML Commonmark is currently the de facto standard for all content created with our implementation of CKEditor (work package descriptions, comments, wiki...). CKEditor.
BlockNote does support exporting it's content to Markdown, but the datasets are not exactly compatible. Additionally, exporting content to Markdown is referred to as "lossy" by BlockNote, meaning we lose editor data on export.
If we want to support Commonmark on BlockNote we will have to do an extensive investigation and work to be able to handle present it.
## Additional questions
Supporting markdown might not be related only to Documents, but also for work package descriptions, comments, wiki, etc.This means we have to be able to handle APIs which currently work with markdown.
* What are the consequences of dropping support for markdown?
* What if we use a different standard of markdown?
* What if we we don't use HTML for tables for example?
* What consequences are there for the API consumers?
A custom version of commonmark combined with some HTML
BlockNote does support exporting it's content to Markdown, but the datasets are not
If we want to support Commonmark on BlockNote we will have to do an extensive investigation and work to be able to handle
## Additional questions
Supporting markdown might not be related only to Documents, but also for work package descriptions, comments, wiki, etc.This means we have to be able to handle APIs which currently work with markdown.
* What are the consequences of dropping support for markdown?
* What if we use a different standard of markdown?
* What if we we don't use HTML for tables for example?
* What consequences are there for the API consumers?