Shall I use CKEditor 5 instead of CKEditor 4, is it better?

Follow

Comments

1 comment

  • Avatar
    Chris Harris

    We have been using CKEditor 4 for some years, and since support is to be dropped soon, I have just spent several days working on migrating to CKEditor 5. This has been a frustrating experience, and as a result, we will probably be moving to some other alternative instead. 

    My frustrations with CKEditor 5 include:

    1. There are few features by default, and every new feature needs a different plugin, each one needing research and time to add in.

    2. Adding plugins is not a simple download/install. Each one needs editing the main build config file, doing a rebuild, working out the config we want, putting it in the build config file, building again. None of which is difficult, but certainly more hassle than I would expect.

    3. CKeditor 4 had a re-sizeable window, CKEditor 5 doesn't. Adding CSS3 resizeable works, but had some odd effects when changing focus from the editor to the page outside it (the window would resize to its default size). I'm not saying that's the fault of CKEditor 5, but it's another example where bringing it up to 4 level is not simple.

    4. CKeditor 4 used inline element styling for e.g. floating an image left/right. CKEditor 5 doesn't, it adds a class to the element. So the code produced by the editor doesn't work right without additional styling, which adds complication to the deployment of the code it produces.

    My research suggests I'm not the only one who would like a simple download that provided the same functionality as CKEditor 4, but it's not available - by design. And I've come to the conclusion that the design of CKeditor 5 has been driven ideologically, providing something that the creators think developers ought to want - rather than something they really do want.

    0
    Comment actions Permalink

Please sign in to leave a comment.