Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Markdown support? #709

Closed
maxn0d3x opened this issue Apr 9, 2019 · 17 comments
Closed

Markdown support? #709

maxn0d3x opened this issue Apr 9, 2019 · 17 comments

Comments

@maxn0d3x
Copy link

maxn0d3x commented Apr 9, 2019

this editor.js supports Markdown editing or even converting option?

@gohabereg
Copy link
Member

Hi @NiNJAD3vel0per !

We will work on some converting options in the next releases

@maxn0d3x
Copy link
Author

Hi @NiNJAD3vel0per !

We will work on some converting options in the next releases

Can't Wait!

@koliyo
Copy link

koliyo commented Apr 10, 2019

Related to #682

@iiDestiny
Copy link

iiDestiny commented Apr 25, 2019

want to support markdown

@cschweda
Copy link

cschweda commented May 3, 2019

Markdown, please. :)

@cong5
Copy link

cong5 commented May 6, 2019

Would you like support markdown?

@appernetic
Copy link

appernetic commented Jun 8, 2019

Yes, markdown, please! :-)

@neSpecc neSpecc added the epic label Jul 2, 2019
@alxlion
Copy link

alxlion commented Dec 2, 2019

Is someone developing this feature ?

@timtody
Copy link

timtody commented May 20, 2020

any updates on this?

@Zulcom
Copy link

Zulcom commented May 20, 2020

I tied to make my implementation with mdast but this is really hard to maintain "CLEAN data that easy to sanitize, extend and integrate with your logic" with markdown.
Example of clean data:

On this page you can see it in action — try to edit this text.

will be

{
  "type": "parahraph",
  "data": {
    "text": " On <b>this page</b> you can see it in action — try to edit this text."
  }
}

Which means you literally should re-implement ALL built-in inline tools to support markdown because we have HTML tags inside "CLEAN data" at this point. And idk how to do it without forking and changing core code

@phanirithvij

This comment has been minimized.

@GauravRajSharma
Copy link

Actively watching this. Markdown input -> blocks -> output Markdown would be a godsent feature for editor.js

@tvvignesh
Copy link

tvvignesh commented Sep 2, 2020

I tied to make my implementation with mdast but this is really hard to maintain "CLEAN data that easy to sanitize, extend and integrate with your logic" with markdown.
Example of clean data:

On this page you can see it in action — try to edit this text.

will be

{
  "type": "parahraph",
  "data": {
    "text": " On <b>this page</b> you can see it in action — try to edit this text."
  }
}

Which means you literally should re-implement ALL built-in inline tools to support markdown because we have HTML tags inside "CLEAN data" at this point. And idk how to do it without forking and changing core code

@Zulcom I was wondering how they are doing bold and italics and looks like the HTML tags are indeed mixed with the data as seen in the online demo. They say about inline elements in the docs and maybe markdown elements are meant to be inline 🤔 :

Capture

I guess they would be following the same approach for markdown as well.

@subwaymatch
Copy link

This would be a killer feature 🙏🔥🌪!

@taurenshaman
Copy link

taurenshaman commented Feb 4, 2021

MarkdownBlock: add Markdown Block support: #1500

editorjs-markdown-parser in awesome-editorjs is not suitable for me, so I created another one: markdown-block

demo:
image

BlocksEditor-MarkdownBlock.mp4

youtube

@rlindskog
Copy link

rlindskog commented Mar 31, 2021

I tied to make my implementation with mdast but this is really hard to maintain "CLEAN data that easy to sanitize, extend and integrate with your logic" with markdown.
Example of clean data:

On this page you can see it in action — try to edit this text.

will be

{
  "type": "parahraph",
  "data": {
    "text": " On <b>this page</b> you can see it in action — try to edit this text."
  }
}

Which means you literally should re-implement ALL built-in inline tools to support markdown because we have HTML tags inside "CLEAN data" at this point. And idk how to do it without forking and changing core code

I'm messing around with using turndown to parse the paragraph blocks, so far I'm having some good luck. I'll post my progress here, might have a package up in the near future.

@MatthewCaseres
Copy link

I'm messing around with using turndown to parse the paragraph blocks, so far I'm having some good luck. I'll post my progress here, might have a package up in the near future.

This would be great. unified.js tools might work for this as well.

@codex-team codex-team locked and limited conversation to collaborators Jan 17, 2022
@talyguryn talyguryn converted this issue into discussion #1870 Jan 17, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests