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

WYSIWYG Markdown support #3192

Closed
LifeIsStrange opened this issue Oct 9, 2020 · 2 comments
Closed

WYSIWYG Markdown support #3192

LifeIsStrange opened this issue Oct 9, 2020 · 2 comments

Comments

@LifeIsStrange
Copy link

LifeIsStrange commented Oct 9, 2020

Next generation editors allow WYSIWYG Markdown support such as slate and Tiptap.

Explanation of this awesome feature:
Markdown as of today is underused as the changes it will do are not visible while editing but this doesn't has to be the case:

As you can see in this demo[0], just outline a word with * and it instantaneously become italic.
What's more: if you start a new line with # it instantaneously get the right size.
You want an h2? Just put 2 ##
It's just plain instantaneous and therefore user friendly and productive Markdown.

[0] https://tiptap.dev

The WYSIWYG that quill already provide is complementary and is quicker to access sometimes and sometimes isn't, especially for doing partial selections, double clicking repeatedly and so much mouse movements "break" the train of thoughts of the writing process, I think this point is important.
What do you think? To me this is the future and is implemented through prosemirror
https://prosemirror.net (but doesn't necessarily has to be)

Also there is a market opportunity here, since as of today there are no WYSIWYG Markdown editors available for Angular (slate being for react and Tiptap for Vue) and since Quill has a great support of Angular, you could adress that market.

@dvlin-dev
Copy link

Slab support it, but quill doesn't support it. It's kind of weird. Can you take a look at this question? thank you. @luin

@quill-bot
Copy link

Quill 2.0 has been released (announcement post) with many changes and fixes. If this is still an issue please create a new issue after reviewing our updated Contributing guide 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants