Better WYSIWYG editors

[discobot]

Gutenberg project is cool… but designed for final users.

Developpers need more fexibility according to projects requirments.

we should be able to choose editor we want for each project !

My proposal is to add and maintain the 3 best WYSIWYG editors to the ClassicPress core !

Let’s vote for that

1. https://www.tiny.cloud
2. CKEditor 5 | Powerful Framework with Modular Architecture
3. https://www.froala.com/wysiwyg-editor
4. Redactor WYSIWYG html editor
5. Mercury Editor: The Rails HTML5 WYSIWYG Editor
6. https://quilljs.com/
7. https://summernote.org/
8. Try before downloading · ContentTools

(it is a quick list, there is still a lot ! add yours…)

---

Read-only archive: Issues · ClassicPress/ClassicPress · GitHub

Author: Yannick

Vote count: 4

Status: Declined (Unactionable)

Tags:

• difficulty-hard
• request-modify-feature

---

Comments

+1 https://quilljs.com

~ posted by Yannick

I vote no.

~ posted by John

okey, why ? any details ? i m interested

~ posted by Yannick

If you add 3 different WYSIWYG editors to the core, then every single user has 2 needless editors on their site. This is bloat.

~ posted by John

A definite no from me too. We are aiming to bring back the “Clean, Lean and Mean”. Adding 3 different editors is the opposite of that, IMO.

~ posted by Pieter Bos

yes, following your comments, we can remove tinymce too and create a config panel to choose which editor to install.

~ posted by Yannick

I vote no too for the reasons given by @John and @Pieter Bos. It’s also worth pointing out that neither Redactor nor Froala is free, so they shouldn’t be on the list anyway.

This is plugin territory.

~ posted by Tim Kaye

I vote no, too. Its plugin territory, and there are already a few plugins doing exactly that. Theoretically (and practically, too) you may even go as far and replace the whole editor with custom textareas based on ACF and not have a care for the rest.

~ posted by Fabian Wolf

Also think about compatibility and work to implement that and support inside a big project like wordpress.
Usually is better to have a list of pros/cons about why we need to switch and support other editors.

~ posted by Daniele Scasciafratte

I’d like to have native Markdown support, personally. And get rid of wpautop.

However, TinyMCE and WordPress are very, very deeply tied together, with a shared history going back many years. This would be far more difficult than you might expect.

~ posted by James Nylen

+1 for Markdown

~ posted by Pieter Bos

If we’re voting for integration with other languages, then I’d like to see LyX or LaTeX support. (But that’s probably just me!)

~ posted by Tim Kaye

+1 for getting rid of wpautop, that thing is horrible.
+1 for no, no additional wysiwyg.

However, please bring the full-blown TinyMCE back, like Advanced Editor Tools – WordPress plugin | WordPress.org

~ posted by Peter Molnar

I’ve started a separate petition for bundling the Advanced Editor plugin here:
https://petitions.classicpress.net/posts/173/bundle-advanced-editor-plugin

~ posted by majick

[anon71687268]

Just noting that we do have a dedicated WYSIWYG editor plugin for ClassicPress.

https://codepotent.com/classicpress/plugins/enriched-editor/

[BTclimb]

@anon71687268 clicked on your link and get redirected to example.org.
Can’t get to https://codepotent.com/ at the moment

[anon71687268]

I don’t see anything amiss on this end. Tried in several browsers and also while logged-in and logged-out. The site seems to be working fine. Here’s a link to the downloadable if the issue persists for you.

[viktor]

This petition will close. At this time no action can be taken on this petition. There is currently an effort to upgrade TinyMCE from v4 to v5 and it’s a large effort since it requires a lot of work to function in ClassicPress core. There’s also a lot of work that needs to be done to make it backward compatible.

Providing multiple editors isn’t feasible or necessary for the core. If there’s a need, a plugin developer can create a plugin to introduce a new editor to replace TinyMCE. But that needs to be in a plugin, enabled on individual websites as needed so it doesn’t affect all CP users.