The rest API has made headlines over the past 12 months, but there has traditionally been important recent work in the areas of WordPress core theme directories and plug-in directories. The plug-in catalog version 3 is moving to the interim release at the end of June, so now is a good time to look at projects down the pipeline. This is a potentially important development for plug-in authors and users, and one of the most important changes on the platform this year. In this article, we will prepare a highly anticipated upcoming release and discuss future changes to the areas of search, tagging, evaluation, and comment in stages. The
Let’s briefly summarize the story so far, and then get started. The latest version path of the plug-in directory is the two directories of WordPress. The first one is the theme directory in early 2015. It is somewhat surprising that a large-scale adaptation has been carried out for the first time since 2008. It can be seen from the notes of Konstantin obenland after its listing that these two changes contain new content. Then there is face lift and some serious technical readjustment. One of the most important departures here is undoubtedly to stay away from bbpress. This change in itself has considerably mitigated the prospects for future development. The
Today’s word press plug-in directory. As the improved theme directory was highly praised, it was natural to focus on the relatively crude plug-in directory. Rapid design adaptation is the most important issue. There is a new theme that can dispel the long-standing grievances on the table. However, the more serious redesign is always on the card. The formal proposal for version 3 of the plug-in directory was officially released in early 2016, and the tentative release date is late June \/ early July. Entering the final stage of development and propulsion is a good time to choose what can be expected when it lands. The
The project overview of plug-in directory version 3 clearly points out that plug-in directory version 3 revolves around three broad focus areas. User roles and responsibilities: improve the front-end interface of plug-in creators and reviewers and better integrate the system. The goal is to make it easier for users to use the plug-in directory as a whole. Interaction with other systems: the directory itself is the data repository of the current plugins API, and can be connected to plugins SVN repo, support forums and glotpress in various degrees. All changes must be managed in a stable manner and remain compatible with previous versions. Replace the old system: a huge change here is to get rid of bbpress and make the plug-in API completely driven from word press itself. Even after a quick reading of several detailed feedback on the welcome project launch and release, I still have a repressive desire for major changes to the plug-in directory, which is enough to show that in order to promote this, the idea of the wider community is not insufficient The
So far, the work of the latest version has been progressing smoothly. Milestone zero, aiming to become the minimum executable product for the startup project, was soon launched. Mil stone 1 and mil stone 2 have also been completed, focusing on smooth submission, comments, and author management dashboards. The white board snapshot released by the design team can make you keenly see what happens next. With the acceleration of the overall speed of the project, the activities of related labels in make channel also began to increase significantly. It is worth mentioning that both posts are a discussion of information architecture considerations and several pointers to possible design directions. In the next section,
It will be more tightly integrated into the configuration file and more accessible to developers through plug-ins. In the future milestones section of the summary project overview page, you can still see the focus on the following releases. Thanks to the rest API, it is usually difficult to feel that the theme and plug-ins will change dramatically, but the third round of plug-in directory will become the long-awaited modernization of various core functions. The conversion from bbpress to appropriate WordPress requires a handsome emptying of the directory so that future development can be carried out more actively. Search improvement may become a low price in the game chain for user experience. This is not only the proof, but also on the pudding, so we are very concerned about the final UI and future development. Are there any specific aspects of version 3 of the plug-in catalog that you are looking forward to? Please contact and inform us through the following comments! Stevepb’s recommended pictures.
