-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Feature: WYSIWYG editing #375
Comments
Hi @sedrubal |
Maybe something like CKEditor Markdown plugin or Hallo.js would serve the purpose? It's definitely something that can reduce the entry barrier for non/less-tech users. |
Though I think it is a good aspiration, markdown is So. Very. Simple. -- even for "normal humans" that personally, not that this is a vote, I think it is a red herring to pursue this unless it is stupid simple to implement, bullet proof accuracy, and most importantly, it has to render the markdown cleanly. HTML WYSIWYG editors, to this day are total crap, and hence people generally don't use them. Granted Markdown is far FAR simpler and better defined than HTML, but... I am skeptical of the value of this. I remain open to it though. |
Before we add a WYSIWYG editor we should simply add a video as how-to. Learning markdown is something you can do in less than 10 minutes. Add such a video to HackMD takes us less than 20 Minutes. Add a whole WYSIWYG editor takes hours. And for most HackMD users it adds no benefit. Even more, I think it can make HackMD worst. Let me show you a few 10 Minute videos to use markdown: Everything a new user needs to know in a very efficient way. Maybe we need to produce an own video for HackMD because, for example, this video is for another Markdown for another parser than HackMD uses. But there are tons of videos about markdown basics in 10 minutes on youtube. Pick one and place it. Way easier and efficient than implementing a WYSIWYG editor. |
I think it would be a huge win to have this functionality. I agree with @taw00 in that markdown already IS dead simple and I personally prefer to write markdown directly. But I work with a couple of so called "normal humans" and I could only convince them to use markdown as the format for internal notes and quick write ups since I found Typora. I believe there are two things essential to reducing the entry barrier:
The toolbar should be rather simple to implement. But the WYSIWYG mode would probably be the breakthrough for adoption by my colleagues. |
Slate.js popped up on my radar today. It looks like a rather compelling
possible option. Not sure if it supports markdown wysiwyg though.
https://github.com/ianstormtaylor/slate
…On Mon, 17 Apr 2017 at 01:17 eipiminus1 ***@***.***> wrote:
I think it would be a huge win to have this functionality.
I agree with @taw00 <https://github.com/taw00> in that markdown already
IS dead simple and I personally prefer to write markdown directly. But I
work with a couple of so called "normal humans" and I could only convince
them to use markdown as the format for internal notes and quick write ups
since I found Typora <https://www.typora.io/>. I believe there are two
things essential to reducing the entry barrier:
- *Point and Click* access to basic features (bold, headline, bullet
list, etc.). A Simple toolbar should do the trick.
- No need to *switch between a "source code" and a result*. In my
experience non-hackers have a subjective feeling of complexity as soon as
they have to switch to a source code.
The toolbar should be rather simple to implement. But the WYSIWYG mode
would probably be the breakthrough for adoption by my colleagues.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#375 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAdr398UDcO7q47spqzsWrEZknvWjDKCks5rwhUFgaJpZM4MRkE0>
.
|
Hi, just want to say WYSIWYG is a huge different to "normal users", programmers are accustomed to logical rules which lead to desired output, but changing between the context is a bit annoying, and not being able to see the result directly on what is edited is more annoying, especially when the user cares a lot about the format, layout, feeling and looks of the text and paragraphs... etc., of which not usually cared about in markdown document. And also I want to mention that(still, imo), a WYSIWYG editor with markdown support and a markdown editor are two very different things, it's more like we have to make a working WYSIWYG editor, and try to translate the output back to markdown. |
(I love hackmd and I use it for work and personal stuff. Thanks for making it! I hope lots of people make a financial contribution.) IMHO adding WYSIWYG support would be the start of bloatware. You cannot optimize for two distinct groups of users simultaneously. If you try, you will end up with a sub optimal compromise in the middle. And why would you? Hackmd is perfect for the programmer/tech writer. Less techie audiences are already served by Google Docs and the like. NB. If you are looking for a way to convert WYSIWYG-y documents into Markdown, there's the excellent Pandoc already. |
Maybe implementing a toolbar like the one in the GitHub Markdown editor could be added. It would allow users to experiment with these to find out how to format text and learn Markdown along the way. For more complex stuff like tables, buttons could generate an empty skeleton that the user can fill in with content, something like this:
Simple tools like this would be a good compromise in my opinion and pairing this with commonly used text editing shortcuts (like There's already something quite similar for Atom, |
I forgot to mention SimpleMDE, which is a compromise between WYSIWYG and pure markdown,on which you see the result on the markdown text directly, but I can imagine some people would find it pretty annoying. To have some editing options is quite nice though. |
I think HackMD is not about to change the whole editor framework. So the discussion about toolbars etc is one that should be discussed in the codemirror repository. Or even easier: Write a plugin, file a PR and we will see what happens. Because this way HackMD can simply work like it is now until your work is done. And no-one has to rewrite a bunch of code just to fit the new editor framework. There are already tons of plugins which add a toolbar in one or another way so simply modify them and try it. :) |
There seems to be a toolbar in the latest builds on https://hackmd.io/features?both |
So did hackmdio discard their community builds or why is this still not in this repo ? |
What's the status here? We can also read it in the changelog... |
+1 |
Current state of the project will receive an announcement later this week: #531 (comment) . Issue #531 is the place to go if you wish to discuss that. let's keep our focus on the WYSIWYG in here. |
I actually don't see a WYSIWYG editor comming. Neither planned nor wanted. So I will close this issue as wontfix. Of course ideas and pull requests are welcome but keep in mind we are a markdown editor and most of them don't go the WYSIWYG way. Actually I really dislike editors that go this way. If you think there has to be such a mode, feel free to reach out in this issue, but for now I'll close it. |
I totally agree and I think the current solution (toolbar with the most important formatting features) is enough. |
Please notice the toolbar is not part of HackMD CE. Right now it's only available on HackMD.io and HackMD EE. |
Thanks for that clarity :) I would like to humbly propose a measure to prevent confusion around CE/EE/hackmd.io: what if there were one place where these feature choices and restrictions are explained, so that the rationale is easy to share in issues like this. Then folks like us here (who might otherwise be confused) can understand that rationale, which I genuinely trust to be well-considered! Thanks for your consideration! |
Please check the community announcement: #579 Actually there are no restrictions on CE besides the need of development by the community. In general if you search for a more interactive place reach out on Gitter or #hackmd:matrix.org. |
I would certainly want a WYSIWYG editor. But I've never ever seen such an editor that worked well in all cases, and I believe I've tested around 10 of them. So I'm cool with closing this ticket. |
hackpad was the best wysiwyg editor imho, and the way they formatted/rendered was technically compat with markdown, though exporting as markdown was kinda de-emphasized. My impression is that the codebase was messy though, and so the editor was not really extractable. And lots of dead forks lay in its wake:
just my 2c :) |
Even though this is closed, I think it is the best place to keep collecting related information. Here's a markdown WYSIWYG editor: |
Interesting, thank you for sharing. |
I don't understand the downside to this. Wouldn't it just be a setting users can toggle so that the users like us who prefer raw markdown can type it out but average users can get a visual interface? There is a lot of untapped potential from people who currently use overkill platforms like google docs or are stuck with mediocre text editing apps like etherpad lite. |
@thekyriarchy two things:
No matter what we are currently on an implementation for a toolbar which makes stuff a lot more user friendly. But I still wouldn't call people who are not willing to write markdown our target audience. |
I somewhat disagree on "wanted" or "target audience". I would totaly welcome a WYSIWYG editor, but the resources needed to add and maintain one are simply not there. The closing of this ticket was also supposed to reflect "don't hold your breath" because this is not something anyone is working on right now. |
That's a good new feature, but not even remotely the same. |
ProseMirror is a notable structured editor, that can be configured for various document schemas, including one matching markdown elements. Here's an example with bidirectional mapping — you can toggle between WYSIWYG editing and editing the source: |
Fix checksums of mermaid
Hi all |
Hi @oceatoon, |
Thx @jackycute |
Zen mode is still under WIP as mentioned PR. |
It was great if you can edit the content directly by editing the rendered markdown like a what-you-see-is-what-you-get editor. So hackmd was usable for non hackers 😉
The text was updated successfully, but these errors were encountered: