Matt said the Editor would be more blocks like and Weston suggested the JS Widgets can be a real contender for this kinda thing. I agree with him on that. I think there are many ways we can tackle the editor upgrade. But even before we jump to any kind of conclusions, it is important to review what are we going to improve. You see, things aren’t as simple as they should be in the case of any other CMS.<\/p>\n
The editing experience is a multidisciplinary product. I am going to list down a few things that I think a modern editor could have inside it and we can see what we can really do out of all this to improve the complete writing experience.<\/p>\n
\u270d\ufe0f\u2014 Content writing<\/strong>: Are we going to load all WordPress admin for just writing an article? We can take inspiration from the Press This here and improve upon that.<\/p>\n \ud83d\udea7\u2014 Editing & Collaboration<\/strong>: Collaboration is by far the most ignored concept when you review the current WordPress editor. Are we going to do something about it, or is that something core shouldn’t have \u2014 not everyone needs it?<\/p>\n \ud83d\udce6\u2014 Previewing<\/strong>: This is another multifaceted problem. I think the new editor can improve upon the gap that exists between what you write and what ends up on the post page. A lot of great suggestions on this part, \u2014 all I’d want to add is that Customize Posts is a good project; maybe we can take another hard look at it.<\/p>\n \u2620\u2014 Revisioning<\/strong>: Revisioning can be very useful. Improving the editor this year \u2014 does that entails improving upon the complete editing\/writing experience or are we just going to develop a particular set of points that are deemed to be more important? IMHO, This is one of the gray areas for the core. A lot can be done to improve upon current workflow of revisions. A lot of WP users are pretty much unaware of how it works. The least I can say is more communication and education about `Revisions` would eventually build a strong user base here. Just a thought.<\/p>\n \ud83d\udea7\u2014 Markdown Support, eh?<\/strong>: Thinking out loud here. Should we?<\/p>\n All of that said, I am pretty excited about this new direction like almost everyone else. I think that we are going to end 2017 with a better WordPress, which will be more user-centric than ever.<\/p>\n Looking forward to contributing as much as I can :)<\/p>\n","protected":false},"excerpt":{"rendered":" Matt said the Editor would be more blocks like and Weston suggested the JS Widgets can be a real contender for this kinda thing. I agree with him on that. I think there are many ways we can tackle the editor upgrade. But even before we jump to any kind of conclusions, it is important to review what are we going to improve. You see, things aren’t as simple as they should be in the case of any other CMS. The editing experience is a multidisciplinary product. I am going to list down a few things that I think a […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"webmentions_disabled_pings":false,"webmentions_disabled":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[10],"tags":[182,146],"class_list":["post-1978","post","type-post","status-publish","format-standard","hentry","category-wordpress","tag-idea","tag-wordpress-editor"],"yoast_head":"\n