Gutenberg editor is one of the biggest changes in the text printing press. But what does the community think of it? In the editor’s comments, we will aim to understand. Since Matt Mullenweg published Gutenberg in wceu in 2017, many articles have reported on it. Only torque has multiple articles on related topics. The next step of WordPress: Gutenberg’s future is great because Gutenberg is ahead of Gutenberg. Therefore, the rest API and Gutenberg work together to develop the future Gutenberg editor of word press. The upcoming Gutenberg editor is set as the method of testing plug-ins. The new editor included in WordPress 5.0 has caused an uproar through the WordPress community Triggered. It will replace the most central aspect of the WordPress back end and check the central way of CMS operation (learn how to customize the classic editor if it is still possible). The
Gutenberg has been used as a plug-in for about a year now, and has reached version 3.0 since the time of writing this article. Many changes have taken place since the first release, and many people have used the editor during this period. Do you like what they see? We’ll find out as soon as possible Next, we created the metaview of gutenberk editor. We looked at the comments in the official directory and articles written on this topic. The goal is to understand public opinion’s views on the upcoming changes. In order to keep the latest version and avoid talking too much about the early version of the plug-in, Gutenberg editor reviewed the summary and focused on the feedback over the past six months. In other words, some old posts will also be included in general comments. The
WordPress community and Gutenberg – under the relationship between love and hate, we will sort out the public opinion on Gutenberg. First stop: WordPress directory. At the time of writing this article in the WordPress plug-in directory, Gutenberg ed more than 200000 times and has been activated in more than 10000 sites. With a score of 2.7 out of 5, more than 500 comments were obtained based on the following evaluation distribution: Male: from this figure, we can see that the theme has been very different. There are many extreme positions and almost no intermediate points. It is also clear that negative comments are more important than positive ones. Let’s take a closer look at what they like and dislike. The
Positive: Gutenberg is a supporter of the new editor: it represents the innovation necessary to catch up with other site builders. It uses modern technology and is moving towards a page builder. In particular, it is closer to the excellent user experience of non coders (including clients), handles the real WYSIWYG experience quickly and easily, and does not need to edit HTML and add custom code. For bloated page builders, the alternative (Gutenberg is not a page builder, but it is important to remember that it is a content editor) page editing options will be merged into one place without being limited by custom shortcut code. Of course, the positive comments also have a lot of suggestions on how to make the editor better. But in these voices, we also have requirements that we should become a part of jetpack instead of leaving Gutenberg as a plug-in or merging it into the kernel. At the very least, users want to provide a simple way to switch back to the current editor as needed. The
As can be seen from the screenshot of the criticism Committee, many people said less flattering words to the editor. Many people fear destroying existing (client) sites, especially those that rely heavily on custom fields and meta boxes. Blocks look complex and cannot generate high-volume content. Compared to the way UI and gutenberk edit HTML
It will break a lot of things. Especially those who build and operate websites for others will feel this. The editor also adds an obstacle for developers to keep plug-ins up-to-date and makes many functions inoperable. The latter affects the entire WordPress ecosystem. As a solution, Iain suggests a longer schedule in order to integrate Gutenberg into the core and use plug-ins for a longer time. In addition, he recommends that this feature be enabled by default only for new sites (not existing sites). This gives people more time to cope with great changes. The
Jeff star the developer of Gutenberg’s idea Jeff Starr also explained Gutenberg. Key point of his comment: keep it as a plug-in. He didn’t think it was necessary to add it to the core because there was already a better page builder. Therefore, the decision is up to the user. In addition, Jeff also highlighted the lack of compatibility with previous versions, and said that in order to make Gutenberg comply with existing extensions, he would perform a lot of tasks. Therefore, the user must be able to choose whether to use. He also offered some suggestions for a smoother transition to the core, but overall he was not the most enthusiastic fan. Vova Feldman – as Gutenberg’s product builder for the future significance of commercial WordPress products, vova Feldman consulted the CEO of the most popular page builders (Beaver builder, element, visual composer) about the new editor. He also provided his own insight. Generally speaking, their views on Gutenberg are quite positive. They praised the innovative method and attracted users with low technology content, believing that it would contribute to the success of WordPress in the market. Of course, the increase of user base will also increase business opportunities. Although it needs to be adapted, the post expresses the general confidence that you can do so. It also encourages those who fear change to look for opportunities that change offers. But the general opinion is that we should not rush to merge Gutenberg into the core. Previous comments below are Gutenberg’s initial public offering comments. But it still contains valid ideas, so it is also included here. Brinda Barron (wpmu DEV) – Post Title: \
TT cromwell- welcome to WordPress for changes in the form of Gutenberg. He loves his writing experience and revisits what Chris Lema said. He is a real front-end editor. He thinks Gutenberg is a good opportunity for WordPress to catch up with its competitors. Report gutenbergreview – don’t underestimate the impact of the flat knot gutenberk editor on WordPress. This is also one of the most divisive issues facing the community before delivery. Supporters claim that it is time for WordPress to innovate the content generation module to remain competitive and attract new users. They look forward to the integration of editing experience and modern technology towards the real connection between content production and final products. The biggest fear of Gutenberg’s opponents is that editors will destroy many existing sites, plug-ins, and workflows. Especially those who work with or for customers. In addition, many people criticized the lack of functions (which may or may not arrive in the future) and whether Gutenberg is only prepared for bloggers and content producers. This is a divisive issue, so many people have called for Gutenberg to be excluded from the core and retained as part of jetpack. Alternatively, you can split word press into classic and updated versions. At least, people want to implement it gradually, so the community has more time to prepare. This theme will continue to inspire enthusiasm. I hope we can finally solve the main problems and find an intermediate method suitable for most people. What do you think of Gutenberg? Where do you stand in the discussion? Please let us know in the comments section below!
