React Draft Wysiwyg
jpuri.github.io
React Draft Wysiwyg
1–10 of 45 posts
Re: React Draft Wysiwyg
#2[EDIT: Just for reference, the title originally was 'the right way to content manage..']
I'd maybe call this "an" approach, rather than the 'right' approach :)
Already, prosemirror has provided a solid alternative, with things like custom-schemas, which ensure we're no longer in contenteditable-copy/paste hell. There's substance.io and quilljs as well.
Any of these could be the right approach for a particular CMS problem.
Re: React Draft Wysiwyg
#3This looks really good. I'm only missing an option to put in formatted code or something.
Re: React Draft Wysiwyg
#4Nice! p.s. indent buttons don't work (on Firefox)
Re: React Draft Wysiwyg
#5[EDIT: Just for reference, the title originally was 'the right way to content manage..'] I'd maybe call this "an" approach, rather than the 'right' approach :) Already, prosemirror has provided a solid alternative, with things like custom-schemas, which ensure we're no longer in contenteditable-copy/paste hell. There's substance.io and quilljs as well. Any of these could be the right approach for a particular CMS pro…
Mostly the 'right approach' depends a lot on the scale of the site(s) you are managing with it when it comes to a CMS. You really start missing forced structure even with a few content managers, let alone 100s of content managers copy/pasting stuff all over the place.
Re: React Draft Wysiwyg
#6Looks very nice, thanks for the work.
I've been tinkering with Draft off and on for quite some time and I love how powerful it is, however documentation was rather lacking in some areas and this project would definitely help me understand some of the things about Draft.
Too bad there's still only a workaround for block styles (as in setting "style" prop on a whole block instead of using setBlockData method).
Re: React Draft Wysiwyg
#7Since you can't tab or you lose focus of the editor box, I am pressing the "add indent" button but to no avail
Edit: Someone beat me to it, but being 2/6 of the early comments shows that they are important!
Re: React Draft Wysiwyg
#8Doesn't seem to be working on mobile. iOS 10
Re: React Draft Wysiwyg
#9[EDIT: Just for reference, the title originally was 'the right way to content manage..'] I'd maybe call this "an" approach, rather than the 'right' approach :) Already, prosemirror has provided a solid alternative, with things like custom-schemas, which ensure we're no longer in contenteditable-copy/paste hell. There's substance.io and quilljs as well. Any of these could be the right approach for a particular CMS pro…
I just came here to write that I think this is THE right approach for wysiwyg editor. Having a full model of the document tree rather and working from that rather than sanitizing `contenteditable`. I expect this approach to automatically solve many problems that other wysiwyg editors have.
Re: React Draft Wysiwyg
#10[EDIT: Just for reference, the title originally was 'the right way to content manage..'] I'd maybe call this "an" approach, rather than the 'right' approach :) Already, prosemirror has provided a solid alternative, with things like custom-schemas, which ensure we're no longer in contenteditable-copy/paste hell. There's substance.io and quilljs as well. Any of these could be the right approach for a particular CMS pro…
I just came here to write that I think this is THE right approach for wysiwyg editor. Having a full model of the document tree rather and working from that rather than sanitizing `contenteditable`. I expect this approach to automatically solve many problems that other wysiwyg editors have.
Prosemirror still uses contenteditable under the hood though. I actually wonder why that is the case.