Is anyone interested in developing an add-on for Imperavi Redactor to replace CKEditor? We would be willing to provide financial support for such a project.
The integration should be done directly in the core via an add-on and include FileManager and SiteMap.
Is this a later version of the Redactor editor used in c5.7 ? There may be code in the GitHub archives that already does this - or at least, would do this when updated to work with v9.
At the time of c5.7 Redactor was generally disliked and the core changed direction to CKEditor for v8, but maybe it has moved on since then.
There are GitHub issues about replacing CKEditor and past threads on these forums discussing alternatives.
I don’t know if I can be of help here. But I’m sincerely interested in the topic. I hear my boss asking again and again about the implementation of a new text editor or if Ckeditor will stay. As of today we go with @franz’s statement in my post «Future of Ckeditor»:
Yup. It’s been 10 months since I posted that thread, so perhaps an update on thinking is in order.
CKEditor isn’t going to be a long term solution for us. We’re stuck on v4, their licensing model doesn’t make sense for our project, and there’s other options that look better and wouldn’t have the licensing challenge.
In a perfect world, we’d be revisiting the editor experience with Concrete with a pretty open mind as part of bringing in a new editor. The web has changed quite a bit since we pioneered in-context editing way back in 2009, and just sticking a bunch of toolbars within part of the page feels a bit antiquated at the moment. If we’re going to commit months of time to extracting this key piece of technology out, it’d be really great to get a compelling new take on the problem out of it. I don’t want to take our car into the shop and do a complete engine rebuild just to have it putt-putt its way down the street. I want that baby to vroom all the way home. 
Of course, that’s our timeless challenge. If we push Concrete forward to stay in line with modern experiences and expectations, we by definition rock the boat for things that are “working just fine” today. We can make Concrete v10 really cool, but we’ll create migration work for our extension developers and anyone upgrading a site. It’s a bit of a Catch-22. Leave things be, we’re a dated irrelevant platform. Change things to chase the current cutting edge, we’re making it hard for the people who already love Concrete as is.
My current take is:
Keep Concrete v9.x working as it is. Do what we can to encourage people to make plugins to replace CKEditor with Redactor or any other editor as add-ons. I know at one point we tried to make the editor an extendable framework layer. I’m not super confident it’s being used that way all the time, but it’s worth poking at. I think any and all efforts to cobble solutions together around v9 that leaves current sites working more or less as they are today with minimal upgrade effort are well worth exploring. We want to keep eliminating bugs in v9.x and not introduce major new features. Path of least resistance. Long Term Support. Don’t rock the boat.
Concrete v10 gets a bit more of an open approach. I don’t want to change UX just because it’s been 5 years, (I’m dying with this iOS glass stuff, good lord) but I do think once you start playing with Lexical and other similar solutions you can imagine an editing experience that is much more smooth than what we do today. I’d love to explore that. I know a lot of add-ons use CKEditor inline and we’d need to make sure there was a relatively pain-free way to fix/support that, but I also know we can continue to keep v9 running with security updates for a very long time (see v8 currently) and hopefully that mitigates the inevitable “YoU AlWaYs ChAnGe ThINgS tHaT WorKeD FinE!!” response I know we’ll get when there’s real work involved with upgrading.
I don’t know if this helps, and I don’t have any timelines to share, but that’s how we’re talking about this problem internally today.
Hi Franz
Thank you very much for the insight into the further development of Concrete CMS and the opportunity to contribute to it. For me, it is clear that Imperavi Redactor (as a commercial solution) cannot/should not replace CKEditor as an editor. However, development towards a standardized interface for easier integration of third-party solutions would be very welcome.
What I personally like about Imperavi Redactor is the Notion-like editing of content and the highly structured data. The editor features a minimalist interface, clean and pure markup, and good extensibility.
We are evaluating a Redactor lifetime license, and if we can use it in our Concrete CMS projects, that would of course be an added value.
Thanks.
Long story short – we are excited to hear news about the future editor.
Thanks for the update @frz