4 ms·
As someone who used to be part of a team developing one of the most popular in-browser WYSIWYG editors: 1. Browser WYSIWYGs are really hard to make. 2. All br
by Tade0 7y ago
As someone who used to be part of a team developing one of the most popular in-browser WYSIWYG editors:
1. Browser WYSIWYGs are really hard to make.
2. All browser WYSIWYGs are terrible.
Avoid rolling your own WYSIWYG if you can. Even if you have a team of 1500 people at your disposal.
- pjscott 7y agoEspecially if you have a team of 1500 people. One person trying to make a browser WYSIWYG is bad enough; can you imagine how buggy it would be if 1500 people worked on it?
- deleted 7y ago[deleted]
- ryankshaw 7y agowhat would you say are the top few out there now? looking to adopt an editor for a large website
- shijie 7y agoRecently integrated Quill into our app and it is fantastic — as fantastic as a WYSIWYG editor can be, I suppose. It produces valid, sensical HTML as the output, in case you need to take the result and use it in email templates (which was our use case). Highly recommend.
- himynameistimli 7y agoThe WYSIWYG editor on Slack that everyone is hating on is actually Quill-based. And do note that it's always been based on Quill, they just recently added more Blots/Embeds to it.
- gridlockd 7y agoPeople dont want better WYSIWYG though, they just want to turn it off.
- Tade0 7y agoI'm obviously biased and would probably recommend what I was working on(CKEditor), but here are some observations regarding the various propositions: CKEditor 4 excels in two things: -Handling selection - especially tables. -Editing for accessibility. I would recommend v5 though, otherwise you'd be potentially giving my one good friend, who's already very busy maintaining v4, even more work. :D https://textbox.io/ https://textbox.io/ - these guys gave us a run for our money a few years ago with their paste-from-external-source (e.g. Word) capabilities, but I believe they've been since acquired by Tiny. https://github.com/tinymce/tinymce https://github.com/tinymce/tinymce - I think this one is slowly being cannibalized by TextBox. I remember them receiving a lot of funding at one point, but getting nowhere with it. Froala - avoid. It's not really open-source, and judging how support for paying customers works you're not getting your money's worth. Quill - we've never seen them as a threat, so maybe they're not that good? Especially given that Slack thing that's currently unfolding. Edit: Formatting.
- andfrob 7y agoTo clear up some confusion around TinyMCE and Textbox.io. The products came to be under the same umbrella due to the merger of Ephox and Moxiecode. The combined company was renamed Tiny last year. TinyMCE version 5, released earlier this year, incorporated much of the Textbox.io features and technology and is the main product moving forward. It is better than Textbox.io in almost every way now and is recommended for new projects. Tiny did indeed raise $4M in venture capital last year. It has not been squandered by any means. In fact, we have only just started spending it as we were profitable and growing when we first raised the money. Tiny has a good-sized development team with more than 30 people in engineering, QA, design and product management. Of the many options out there, TinyMCE is a good bet! (disclosure: I am a founder and the CEO at Tiny)
- bhl 7y agoHow do you feel about ProseMirror, and what browser WYSIWYG editor did you work on if you don't mind? I'm using it right now to build a personal notes editor, but there isn't much open source components to model my custom nodes to.
- Tade0 7y agoProseMirror is not a "batteries included" solution, but rather a framework for creating them, so a lot of the UI stuff is missing and I wouldn't advise using it directly. I worked on CKEditor 4 (very different from v5, which is a rewrite).
- TeMPOraL 7y agoAgreed. Part of me wishes you could just embed MS Word in a webpage if you really need WYSIWYG. Similarity to Word is the reason people want it in the first place.
- bhk 7y agoIs this because WYSIWIGs are inherently hard to make, or because of browser-specific challenges? Was this due to compatibility issues between browsers? I've written my own native Windows WYSIWIG editor and a fair amount of web UI, and was thinking of rolling my own web-based editor.