2017 is coming to an end. This year, WordPress saw 11 public releases and 11 beta or release candidates. People close to the WordPress community may notice that the WordPress world looks larger and broader in some ways. What happened to WordPress in 2017? Many minor changes have set a huge milestone for WordPress’ thinking leadership. If you want to know how WordPress changed quietly in 2017, please read on. Innovation support for developers this year, WordPress has built two obvious ways for WordPress developers and editors to improve. For developers, the improvement of rest API is the key. This generation of users are increasingly demanding for websites in terms of speed and agility, not just what PHP built websites can provide. In addition, there are some integrations to consider. E-commerce websites with mobile applications, printed matter and magazines with online participation are all innovating to create new solutions for end users. Untitled word press is increasing, which means that the use of APIs (especially rest APIs) is increasing. So what did WordPress do with the rest API this year? The
In december2016, a rest API endpoint was provided for the content of WordPress 4.7 \
For editors and content creators, WordPress embarked on Gutenberg editor, the largest project since its inception. Some people explain that these changes are to recover the past technical debt. I like Matias Ventura’s description of Gutenberg as tessaeus’ ship or the work of repairing a ship on the way. With the growth and innovation of WordPress, editors are not. As a result, plug-ins and themes depend on the unstable foundation of quick code and page builders. The new editor is designed to make content writers more enjoyable. Gutenberg adjusts the gap between back-end editing and front-end shapes, allowing content producers more freedom to create rich and attractive posts. The
WordPress worked with many community members and participants to create this new editor, and there are reasons to do so. Recently, there are too many uses for word printing machines. No matter what changes are made, there are places that have to be destroyed. In particular, the features of these drag and drop style editors may simply interrupt shortcut code and page builder. The editor is a plug-in that everyone can use and view at present. It is ed more than 500 times a day on average. Before it was provided as a plug-in in june2017, it had been developed for 6 months and 25 updates had been made. Let’s look at the corresponding timeline. The
June 16: v0.1.0 – WordPress plugin, initial release June 23: v0.2.
It is obviously necessary for a team of developers, editors, and decision makers who are familiar with the site. WordPress 4.9 has brought very useful changes to the team, including error checking for features and code changes that save design changes in a draft manner. The rest API provides an opportunity for the team to extend the functionality of general word press by branching to an untitled word press site or progressive web app. The
If you pay attention to the significant maturity of WordPress core developers, you may also notice the fact that the listing schedule has matured in the past few years. There were 22 WordPress releases in 2017, of which 11 were candidate versions for developer beta and \/ or releases. The team worked with hackerone to quickly release security and maintenance updates. If you know that the community is ready, please post a feature update and remove two or more beta release candidates before the update is made public. Whether it is raining or snowing, whatever can be postponed has been postponed within the predetermined date and time. The maturity of the release schedule of the WordPress core team reflects the maturity of the open source software itself and competent developers. The
What is the future? The future of WordPress seems to be ripe by chance. All directions are changing to support the future of digital experience. Making team work flow more easily has attracted the attention of more and more enterprise businesses. Rest API and Gutenberg have opened the door to more users on the web. State of the word 2017 released the project tide and conducted automated tests on all plug-ins and themes in the word press directory. He also mentioned the partnership with hacker network hackerone, which aims to find loopholes to obtain greater benefits. The
We also look forward to more rest API endpoints, ease of use for writers to create rich and attractive content, and more innovations to provide attractive experiences for mobile and tablet users in the future. Before the release of WordPress version 5, the disconnection between gutenberk pages and rest APIs is expected to be resolved. Finally, WordPress will extend the core code base to meet the basic functions of users who need to add plug-ins and shortcut code extensions before. Yes, WordPress has great potential in the future. I can’t wait to see what’s next.
