Discarding this, as we won't be relying on CKEditor5 as a default.

Its new licensing model presents some challenges to integrate with Liferay DXP, and the current direction of the project makes it very expensive for us to exclusively rely on it. We would either need to cut out current functionality or develop it again.

I like this idea :+1:

I've filed https://github.com/liferay/alloy-editor/issues/906 with it.

I know features is a sticking point, but it's just totalitarian to remove tools that users need.

Why not re-approach features sets as just that. "Sets". Sure offer the default tools you need to get by (including text alignment) but then offer the user the option to expand their tool "set" so if there's a feature that they need it's a click away for them.

• Basic editing

• Technical writing

• Conversational writing

• "All" ... when the user selects all they get every tool available in Alloy Editor

Hey , at this point, after some consideration, we will likely not move to CK5 as default. Motives are:

• Browser Support

• Full HTML (or other languages) support. As it turns out, CKEditor5 follows a similar approach of what we attempted to do with AlloyEditor (fewer features, more focused content creation). Unfortunately, the html generation is way more restrictive, so it's not really suited (as it is) for Web Content and a lot of work would be needed for things Forums and Wiki...

I still need to go over the WYSIWYG epics to reevaluate next steps for our next release.

Given that CK5 won't support IE11, users that require IE11 compatibility at least for now, where does this leave them? Would the level of support drop to read content only in IE as is with mobile right now?

https://github.com/ckeditor/ckeditor5/issues/330