The theme review team should lessen their burden and seek help from the end- users who are the actual beneficiaries of a WP theme. The WordPress rating system can also help. Here are two examples of this in action: 10up Components Library, WPTRT GitHub. All of this should culminate in a complete handbook which is accessible to everyone.
#WORDPRESS THEME 2017 COMMENTS DISCUSSION CODE#
This could help the developers write their code in a better way. One possible solution is to introduce pre-defined component libraries and code snippets. The result is theme rejection which is very frustrating. I’ve been following the team’s discussions, and most of the time they’re struggling with the security and licensing guidelines, which developers fail to follow. The current theme submission guidelines are quite well written but there’s room for improvement. Some problems could come with the addition of this section, and we would have to decide who would choose the themes, but I think having both the featured section as well as the Editor’s Choice Section would bring equilibrium. Just because a theme got approved and ranks high in the featured section, doesn’t mean it has high quality code. Though, I think we can also have a section for Editor’s Choice, which should be a hand-chosen section that features high-quality code and design standards. Which is pretty important, because it is unbiased and automated. The section for Featured themes shows automatically picked entries based on statistics. Efforts need to be put in to produce more of such tools and provide an automated testing environment.Īn ideal environment would include simple test syntax, no implicit globals, tests that run concurrently, and enforced automatic tests. The Theme Check plugin has been around for quite some time and developers rely greatly on it for debugging issues before the final theme submission. It sounds completely illogical to check code issues manually when automated tools can handle the same. We can program things to make our life easier. This not only requires an extra work but also contributes to the long delays.
#WORDPRESS THEME 2017 COMMENTS DISCUSSION MANUAL#
The current workflow requires manual checking for all the bugs and theme standards. Keeping your code in check, every day without you having to look at it. Imagine having an automated theme testing library that you could use in an agile way with continuous integration. I would love to see an automated testing library that tests your code in an agile manner with continuous integration.
![wordpress theme 2017 comments discussion wordpress theme 2017 comments discussion](https://www.jackmolan.com/wp-content/uploads/2017/10/22489793_1324073071054535_439884953403798705_n-768x576.jpg)
![wordpress theme 2017 comments discussion wordpress theme 2017 comments discussion](https://www.lockedownseo.com/wp-content/uploads/2016/07/start-wordpress-seo-768x432.jpg)
It’s time we improve the default demo and build something interesting. This issue is associated with almost every other theme at the. It displays a more blog oriented layout, but it can do so much more. But have you tried looking at its demo? It doesn’t showcase the business layout of the theme. The new TwentySeventeen theme is one of its kind. Themes are more business focused, and we need better demos. It’s 2017, and WordPress is more than just a blogging platform. One of the major issues is the demo layout of the themes. Such automation will also allow contributors/reviewers to spend more time on something productive than doing grunt work. Ideally, it should take approximately 24-48 hours for the theme to be reviewed and get published. With the current reviewing process, scalability seems near to impossible. Scalability of a workflow goes hand-in-hand with automation. As a theme developer, I know how much effort is required to develop your product, and if you spend months building a product and then wait half a year to share it with others, it can kill your mojo. Six-month delays are not good for the ecosystem. It requires an in-depth automation with little human involvement.Īfter all, we are all developers, we can find a way to automate the process. I think that the theme reviewing process should be revised altogether. Many developers including myself have been hesitant in submitting themes to because of the long wait time to get published. After a few iterations, the theme goes live in less than a week. Ideally, a theme developer submits the theme, the theme review bot reviews it and responds back within 24 hours. So, in today’s post, I’m going to dish out somewhat an ideal look of the WordPress theme directory. Matt Mullenweg’s biggest dream for the repository is for it to be the main place for users to search and find themes.
![wordpress theme 2017 comments discussion wordpress theme 2017 comments discussion](https://themesharbor.com/wp-content/uploads/2020/03/th-discussion-settings-1-1024x395.jpg)
The future of the theme repository on has been in discussion for quite some time, but after the recent launch of the new plugin repo, I think that it’s high time to discuss the theme repo as well. The theme repo is flooded new entries on a regular basis but, how many actually make it to the list? The answer is - very few. However, it has been plagued with long queues, fewer contributors, and a flawed contribution process. The WordPress theme repository is the best place to find safe and beautiful themes.