Skip to content
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

Market CKEditor as Markdown WYSIWYG editor #5721

Closed
zadam opened this issue Nov 10, 2019 · 9 comments
Closed

Market CKEditor as Markdown WYSIWYG editor #5721

zadam opened this issue Nov 10, 2019 · 9 comments
Assignees
Labels
squad:ccx Issue to be handled by the CCX team. type:docs This issue reports a task related to documentation (e.g. an idea for a guide).

Comments

@zadam
Copy link

zadam commented Nov 10, 2019

📝 Provide a description of requested docs changes

Just an idea - in certain communities Markdown is very popular and essentially gold standard for text editing, documentation, publishing etc. Many apps use split view approach to editing where you enter markdown in one pane and it is rendered in another pane - I consider this pretty bad UX, but there's also a new breed of WYSIWYG markdown text editors which try to combine the best of both worlds - simplicity and "just text" writing and realtime feedback and rendering all in one.

And I think that CKEditor is actually such an editor - it supports Markdown output but also a bit hidden Markdown input.

The problem is that it's not well known that CKEditor can work like a complete Markdown WYSIWYG since it is not marketed as such. Those two critical features mentioned above are isolated, not put into larger context. Autoformat documentation does not even mention it uses Markdown syntax.

Of course CKEditor does not support Markdown perfectly and in some aspects probably never will, but there is a big range of what people actually need/want from Markdown - e.g. for some it's mostly about having mostly keyboard oriented writing using familiar syntax without toolbar clicking. What CKEditor loses on imperfect Markdown support gains on the feature richness and maturity compared to those other markdown WYSIWYGs.

What I had originally in mind was that you could start by putting up a documentation page and/or blog post "How to configure CKEditor as a Markdown WYSIWYG" to spread the awareness and get some hits from google.

@zadam zadam added the type:docs This issue reports a task related to documentation (e.g. an idea for a guide). label Nov 10, 2019
@Reinmar Reinmar self-assigned this Nov 18, 2019
@Reinmar Reinmar added this to the backlog milestone Nov 18, 2019
@polarathene
Copy link

The markdown support should be improved with a recent PR updating it? No idea how that impacts the autoformatting feature.

One of the devs I work with evaluated CKEditor but stated it didn't support Markdown input(as a source, although I guess one could convert markdown to html each time?) or a editing mode. They didn't seem to be aware of this inline editing support for Markdown, probably because as this issue cites, it's not easily discoverable, I only found out after finding this issue and trying it out.

Reddit provides a toggle to switch between richtext and raw markdown editors, while Github does raw markdown with GUI toolbar support. Probably should be a separate issue but would be nice to see CKEditor have that sort of flexibility if possible. Another variant uses raw markdown but applies styles to the font style and size based on markdown features while still retaining the raw markdown syntax.

@fredck
Copy link
Contributor

fredck commented Dec 18, 2019

One of the devs I work with evaluated CKEditor but stated it didn't support Markdown input(as a source, although I guess one could convert markdown to html each time?) or a editing mode.

Have you checked the following at the CKEditor 5 documentation?
https://ckeditor.com/docs/ckeditor5/latest/features/markdown.html

A properly configured editor definitely accepts markdown on input and output.

@fredck
Copy link
Contributor

fredck commented Dec 18, 2019

Reddit provides a toggle to switch between richtext and raw markdown editors, while Github does raw markdown with GUI toolbar support. Probably should be a separate issue but would be nice to see CKEditor have that sort of flexibility if possible.

CKEditor will cover the richtext editor part. Then, it's up to the implementation to decide what kind of editing workflows are necessary, eventually making it possible to switch between CKEditor and any other kind of editor (markdown or not).

@Reinmar Reinmar removed their assignment Aug 18, 2020
@AnnaTomanek AnnaTomanek added the squad:ccx Issue to be handled by the CCX team. label Oct 19, 2020
@godai78
Copy link
Contributor

godai78 commented Nov 6, 2020

This issue #7924 nicely fit into this aim, too.

@godai78
Copy link
Contributor

godai78 commented Nov 13, 2020

"How to configure CKEditor as a Markdown WYSIWYG" - well, that would be a seemingly simple task. Just use autoformatting and Markdown output ;)

@zadam
Copy link
Author

zadam commented Nov 13, 2020

Yes. I know that, you know that. 

But people evaluating CKEditor as a component for their new application don't know that. 

These features are not well advertised. Autoformatting page doesn't even mention that the syntax is actually Markdown. If you don't closely read this documentation (which you typically do once you already made your decision to use CKEditor), you won't realize CKEditor has these capabilities.

@godai78
Copy link
Contributor

godai78 commented Nov 13, 2020

Well, it DOES mention now, it's just waiting for a review.

@godai78 godai78 self-assigned this Nov 16, 2020
@godai78
Copy link
Contributor

godai78 commented Nov 27, 2020

@zadam, I guess you may like this blog post: https://ckeditor.com/blog/CKEditor-5-the-best-open-source-Markdown-editor/ ;)

@zadam
Copy link
Author

zadam commented Nov 27, 2020

@godai78 Awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
squad:ccx Issue to be handled by the CCX team. type:docs This issue reports a task related to documentation (e.g. an idea for a guide).
Projects
None yet
Development

No branches or pull requests

6 participants