The WordPress Theme repository is the best place to find safe and beautiful themes. However, long queues, fewer participants and flawed contribution processes make them difficult. The topic repository is regularly filled with new items, but how many items are included in the actual list? The answer is – very few. WordPress The future of the theme repository of. Org has been discussed for a long time, but with the recent introduction of a new plug-in repository, it seems time to discuss the theme repository. Matt Mullenweg’s biggest dream for the repository is to become the main place for users to search and find topics. The
So in today’s article, I will show you the ideal look of WordPress Theme Directory. The ideal situation of the automated review process is that after the topic developer submits the topic, the topic review robot will review the topic and respond within 24 hours. After several repetitions, the topic will be published in less than a week. WordPress, because many developers, including me, wait a long time to release. I hesitate to submit a topic to org. I think the seminar course should be fully adapted. Deep automation is required, with little human intervention. Ultimately, we are all developers who can find ways to automate the process. A delay of six months is bad for the ecosystem. As a theme developer, I know how much effort it takes to develop your product. Then you spend a few months making products. In order to share them with others, after half a year, your will will will disappear. The
The extensibility of workflow is combined with automation. The current review process can hardly be extended. Ideally, it would take about 24 to 48 hours to review and publish the topic. Through this automation, contributors \/ reviewers can spend more time on more efficient work rather than lengthy work. One of the main problems with better custom presentations is the presentation layout of the theme. In 2017, WordPress is more than just a blog platform. The topic is more business focused and needs better presentation. The new tweetyseventeen theme is one of them. But do you want to see the demo? The business layout of the topic is not displayed. The
Shows a blog centric layout, but can perform more tasks. This question is WordPress. Org covers almost all other topics. Now it’s time to improve the basic presentation and build something interesting. I want to see an automated test library that tests code in an agile manner through continuous integration of automated topic tests. Imagine that you have an automated topic test library that can be used flexibly through continuous integration. View the code every day without having to view the code. The current workflow needs to manually check all errors and subject standards. This requires not only additional work, but also a long delay. The
As I said, we are developers. We can program to make life easier. When automated tools can handle the same problem, it sounds completely illogical to manually check for code problems. The theme check plug-in has been used for a long time, and developers rely heavily on it to debug problems before submitting the final theme. But this alone is meaningless. We need to strive to produce more of these tools and provide an automated testing environment. The ideal environment includes simple test syntax, implicit global, simultaneous tests and forced automatic tests. The
The recommended topics section of the \
I think Sean can have it, too. This section should be a direct selection that features high quality codes and design standards. The subject has been approved. A high ranking in the recommended part does not mean that there is high-quality code. Adding this section may cause some problems. It is necessary to decide who will choose the theme, but I think it will bring balance to have both the special section and the editor’s choice section. The
Improved submission notes the current subject submission notes are well written, but there is still room for improvement. I have been following the team’s discussions, and in most cases, security and licensing guidelines are not followed by developers. The result was a very disappointing subject rejection. One possible solution is to introduce predefined component libraries and code snippets. This may help developers write code in a better way. All of this must end in a complete manual that is accessible to all. The following are two practical examples of the 10up component library and wtrt GitHub: The
Trust the user, and the WordPress hierarchy will also help. The thematic review group should lighten the burden and get help from the end users who are the actual beneficiaries of the WP theme. It’s time for users to believe in good topics and bad topic evaluations. Therefore, you can use the evaluation system to help. The connected plug-ins plug-ins and themes are already connected. In most cases, you will find people who have disputes about the topic and plug-in areas. End users will use both. What if you could have a plug-in section associated with the topic? The theme creator can select several plug-ins that match the theme. About how? I think everyone will like it. The
As a WordPress developer and user, I want to work with many others to see these changes in real time. These are just a few suggestions that I personally think should be integrated. If you now have more shared content about the WP topic repository, you can do so. Please share your feedback in the comments below and tell me what you think of this post. Finally, you can view all my articles on my profile page, follow me on my blog or contact me at [email protected]. Write the development workflow according to the idea of WordPress. The
Don’t hesitate as usual. Please leave questions or comments below. I will answer every item.
