SeNioR-

It's not easy to switch to CKEditor 5. 
Source: Migration from CKEditor 4

It seems to me that IcoMoon is now only used for installation / update and in development mode. 
Admin
admin\install\css\fonts.css  admin\install\css\misc.css admin\install\font\icomoon.eot admin\install\font\icomoon.svg admin\install\font\icomoon.ttf admin\install\font\icomoon.woff admin\upgrade\css\fonts.css admin\upgrade\css\misc.css  admin\upgrade\font\icomoon.eot admin\upgrade\font\icomoon.svg admin\upgrade\font\icomoon.ttf admin\upgrade\font\icomoon.woff  Dev
applications\core\dev\codemirror\mode\sass\test.js CKEditor
applications\core\interface\font\icomoon.eot applications\core\interface\font\icomoon.svg  applications\core\interface\font\icomoon.ttf  applications\core\interface\font\icomoon.woff

A small feature, but it makes me want to click on the tab.
Ref: How to Display Update Notifications in the Browser Tab

I was supposed to write about it 🙂
The logo on the mobile version is slightly blurry, a few versions would solve the case, I think.

I think there are two different use cases:
Editor for user-generated content. Should be simple, not too many options, clear and foolproof. I think that the actual IPS editor fulfills the requirement. Editor for articles wrote by admin. Should be powerful, have many options (text positioning, blocks, columns, grids, custom code pieces, custom styles, extendable with SEO and other plugins, have additional extensions via Marketplace etc.) For this case, the actual IPS editor is not enough. 

Update // September 14, 2021: WE MADE IT! 
After months of hard work behind-the-scenes, we launched our newly-refreshed website and community theme. We have a formal blog post about it on the way, but we wanted to share this soft launch with you first 🤫. Feel free to share your feedback in the comments; we're here for you and are chatting! 
 
Earlier // May 12, 2021:
 


Hey all, Happy Hump Day!
@Charles and I joined forces here in Las Vegas this week because we're planning something super exciting. 🤐😎 
After 4.6 rolls out, we're focusing on freshening up our homepage/subsequent pages and match that branding with this community. That may or may not be an understatement, but if there's anything to take away from this teaser it's that there some slick visual changes on the way!  
If you guys have any websites/homepages which are clean & minimal that inspire you, we'd love for you to drop some links in the comments. We already do have a firm idea/concept planned out, but your opinions matter to us! We'd like to hear from you. 

A Mobile Hamburger Menu with a gesture would make it much easier to use. What do you think about it?
 
Examples:
https://codepen.io/adam2326/pen/YwOqqB
https://slideout.js.org/

ipsButton_split
/* Child */ html[dir='ltr'] .ipsButton_split > :first-child, html[dir='rtl'] .ipsButton_split > :last-child { border-top-left-radius: inherit; border-bottom-left-radius: inherit; overflow: hidden; } /* Child */ html[dir='ltr'] .ipsButton_split > :not(:first-child), html[dir='rtl'] .ipsButton_split > :not(:last-child) { margin-left: -1px; overflow: hidden; } Before

After

ipsToolList_primaryAction
@media screen and (max-width: 767px) { .ipsToolList_horizontal > *:not(:last-child) { margin-bottom: var(--sp-2); white-space: nowrap; overflow: hidden; text-overflow: ellipsis; } } Before

After

ipsMenu_headerBar
.ipsMenu_headerBar a{ overflow: hidden; white-space: nowrap; text-overflow: ellipsis; } Before

After

I miss the "Cancel" button. Can we expect the button in the future?

For me, it is not important which editor to use, but how exactly it will be customized by IPS.

The main thing I hope for is that IPS won't carry over all the same bugs that they added to the current editor and haven't been fixing for years. Such as the complete inability to delete mentions in mobile Chrome, for example:

1620649541089.mp4
As well as get rid of additional overcomplications, such as replacing existing editor functions. For example, fast and easy URL embedding on clumsy and slow:

👍   


👎 

I just moved the members' titles to the custom field.
Just create a new text field with a maximum length of 65 characters.

My field has the ID 7. In the query, change the field ID to yours.
Additionally, add a prefix before the tables, if you have one.
Make an SQL query
UPDATE core_pfields_content t1 INNER JOIN core_members t2 ON t1.member_id = t2.member_id SET t1.field_7 = t2.member_title; Caution.
You do everything on your own accountability.
Before executing the SQL query, make a backup copy of the database just in case.

It's not easy to switch to CKEditor 5. 
Source: Migration from CKEditor 4

I just moved the members' titles to the custom field.
Just create a new text field with a maximum length of 65 characters.

My field has the ID 7. In the query, change the field ID to yours.
Additionally, add a prefix before the tables, if you have one.
Make an SQL query
UPDATE core_pfields_content t1 INNER JOIN core_members t2 ON t1.member_id = t2.member_id SET t1.field_7 = t2.member_title; Caution.
You do everything on your own accountability.
Before executing the SQL query, make a backup copy of the database just in case.

I just moved the members' titles to the custom field.
Just create a new text field with a maximum length of 65 characters.

My field has the ID 7. In the query, change the field ID to yours.
Additionally, add a prefix before the tables, if you have one.
Make an SQL query
UPDATE core_pfields_content t1 INNER JOIN core_members t2 ON t1.member_id = t2.member_id SET t1.field_7 = t2.member_title; Caution.
You do everything on your own accountability.
Before executing the SQL query, make a backup copy of the database just in case.

I just moved the members' titles to the custom field.
Just create a new text field with a maximum length of 65 characters.

My field has the ID 7. In the query, change the field ID to yours.
Additionally, add a prefix before the tables, if you have one.
Make an SQL query
UPDATE core_pfields_content t1 INNER JOIN core_members t2 ON t1.member_id = t2.member_id SET t1.field_7 = t2.member_title; Caution.
You do everything on your own accountability.
Before executing the SQL query, make a backup copy of the database just in case.

@Matt. We love the new feature.  No one is crapping on it.  We just feel the custom titles were a big deal to our old members.  In fact I enabled a group rule to make it a reward when people hit 500 posts. 
We are just asking that you not take that away and delete the user data when upgrading.  Instead find a way to preserve it AND leverage your new system.  They can coexist!
Can you chime in?

It's not easy to switch to CKEditor 5. 
Source: Migration from CKEditor 4

So our members from 20 years of forums use will lose their hard earned titles.  I expect pretty annoyed members.  Can we have both?

CKEditor 5 was made from scratch, and from what i've seen, it works really well. I don't see the point in moving to a different editor.
What we need is Invision to finally decide to migrate to the new version, but because it was made from scratch, t's not a simple upgrade, but rather its a migration and it will give them a lot of work.

Probably the biggest advancement in Single Sign In seems to me to be the ability for everyone who are logged in to their Google accounts is to display the Use FORUM NAME with Google popup - as Reddit and Pinterest do. @Jordan Invision @Matt

😒
Before, it was taking first topic image and it was better. Now default image and it's not interesting to see same image with different topics on social accounts. We're loosing the hits. .

New ranks and achievements is good but the ability to edit Member title and have it below your username needs to stay.

I hope not.
If it has you'd be surprised how popular it is to set your own personal message below your username, instead of whatever the forum decides.
It needs to stay.

CKEditor 4 is reaching the end of life (source). Instead of jumping onto the CKEditor 5 bandwagon, I propose Invision consider an alternative editor. There are many well-established modern editors such as, for example, TinyMCE, Froala, Quill, and Redactor, to name a few. Any of these would make satisfactory alternatives.
 
CKEditor may be 'old school,' but it has become bloated, larger in file size and load time.  Most of the issues it encounters often have to do with responsive layouts on a mobile device and excessive load time. As mobile continues to dominate the landscape, I feel it may be prudent to focus on an editor development that has kept up successfully with the times with the least issues.
 
Changing the editor should not be expected in the next release. But a roadmap should be considered for a future transition.  Thank you for your time and consideration. 😀

We are leaving a lot on the table without this.  IP Pages is ripe for being amp ready.  Blogs too.