There are many WordPress communities, but one thing is for sure. Work efficiency is never low. The last 12 months are a perfect example. During this period, we saw the launch of WordPress 5.0 and the introduction of Block Editor. But the machine will not stop. Matt Mullenweg recently introduced the 9 priorities of the platform during 2019 in his word speech. If you understand what this is, you can see the future development of WordPress. In this post, we will take a detailed look at Matt Mullenweg’s \
Plan for the future: word press the word press team needs to consider two aspects each time it releases a new project or plan. To understand our meaning, please think of WordPress as a duck floating on the water. From above, you can see that the ducks are just gliding and flying. But here is a completely different story, the engine of the bridge and the webbed feet. The same is true of text printing. Clearly, the new plan behind it was carefully planned almost permanently. In sharp contrast, Matt Mullenweg could hardly be seen for a long time before Matt Mullenweg proposed the road to the next 12 months of WordPress. The
Nine projects in 2019: like other recent development efforts such as \
The menu block operation has started, but so far, only charts and pictures are required. Some of these were recently created by the design team in Wordcamp us. On the make WordPress design page, you can read their initial ideas in detail. If you think they can provide insight, you can also participate. 2. transplant all parts of WordPress as blocks. On the contrary, the next work is relatively simple. As you know, WordPress uses the current widget to build areas such as sidebars and footers, and the current option contains multiple functions. The
At this point, the part is not block based and can be accessed through word press and the dedicated part page in the customization program. Future plans are simply to convert all existing assemblies to blocks. Because the block editor is now at the center of how content and layout are created, this is a natural move. 3. ensure that all part editing areas support blocks, and there are two default areas for editing the current part and its contents. In the back-end appearance>widgets, there is an administrator panel and a dedicated part of the custom program. However, these parts are also incompatible with the block editor, which is clearly the opposite of the future direction of WordPress. The
Therefore, the goal is to ensure that these assembly editing areas are fully compatible with the block system. In other words, you must be able to place blocks in the component area and use them as you would in a page, post, or other content type. Whether this is easy to implement is discussed in other articles. However, this depends on the block editor to generate content and layout
Not to mention that this is necessary for future versions of WordPress. 4. on the surface, the method of creating the subject visual registration content area is less intuitive than other projects. But here, the goal is simple. The
The current topic registers the content area under the hood, which is usually set strictly. However, with the Block Editor running, you now have the opportunity to give end users (or developers) more scope to decide where content should \
Male 5 If you are not familiar with the status checking and troubleshooting plug-ins in the WordPress kernel, perform the installation related checks. The focus is on detecting common configuration problems from various other errors. Health check is a plug-in under continuous development, but it has a feature that clearly shows that it should be included in WordPress. The goal is to merge the functions of the plug-in with the core of word press and become a valuable additional function. This plug-in usually provides a built-in way to debug unstable sites while encouraging excellent software hygiene. The
6. provide users with methods to automatically update plug-ins and themes, which is one of the functions word press has lacked since its birth. In fact, many web hosts are comfortable handling updates because they have never implemented a built-in solution. In short, the WordPress site’s plug-ins and themes should be updated frequently. Depending on the number of themes and plug-ins you install, you need to perform updates almost every day. Fortunately, the WordPress team will eventually introduce a way to allow users to automate these updates. Jetpack users know that this feature already exists in a specific plug-in, but they plan to add it to the word press core. The
7. it is not only the theme and plug-ins that make it easier for users to automatically update the word press core. Another goal in the next 12 months is to realize the method of automatically updating word press itself. In other words, many web hosts are available at the basic level, but lack basic functionality. Of course, considering that malicious bugs or supervision may damage the website, you may think that automatic core update is not desirable. However, for those who manage dozens (or more) of websites for customers with low technology propensity, this option may be a gift from God. The
This feature is not available in word press core or dedicated plug-ins, so it may be more difficult to implement than in themes and plug-ins. However, this option must be available at the time of the launch of Wordcamp us2019. 8. wordpress If you navigate to \
Yes. Considering what the central block in WordPress looks like, it is perfect to show it in your own terms. After the project officially starts, you can look forward to its rapid development. 9. in order to process open trac tickets, a classification group was finally established, which is another project already under way. At present, trac has more than 6500 public invoices. Of course, this backlog does not help solve important problems in advance. We are currently reviewing the short-term work of \
