Earlier at the moment, Dion Hulse introduced the outcomes of a six-week survey on the WordPress.org theme add course of. The objective was to determine if importing a ZIP file was a “ache level” and see what different strategies theme authors want. Then, transfer ahead primarily based on the suggestions. In whole, 256 individuals responded to the survey.
Of the weighted outcomes, importing themes through a ZIP remained the most well-liked possibility. Committing through Git or integrating with GitHub got here in second and third, respectively. Utilizing SVN or a CLI instrument additionally had assist.
The subsequent steps ought to embody permitting theme updates to be submitted through SVN. Trac tickets can even be eliminated for updates, which the Themes Staff now not critiques. For theme authors preferring Git, the plan is to encourage the usage of a GitHub Motion for automated deployment over SVN.
There are not any tickets for implementing the modifications but, however they’re forthcoming. Hulse mentioned he’s awaiting any suggestions on the announcement submit or within the Themes Staff September 14 assembly.
Nothing was mentioned in regards to the preliminary theme submission. It will doubtless stay the identical.
The upcoming SVN entry may have some limits compared to plugins. Updates can be saved through a strict /theme-slug/model scheme with a standardized model format. Theme authors is not going to be allowed to vary any commits as soon as an replace is submitted. Just like the ZIP add system, they might want to bump the model quantity to ship a brand new replace. The objective is for the theme repository to merely be a deployment vacation spot and never a spot for development.
This must be a welcome change for many who have longed for various theme add strategies. Way back to I can bear in mind, theme authors have requested for SVN entry to the WordPress.org theme listing. It’s a functionality that plugin builders have lengthy had. This was earlier than the proliferation of Git and the rising reputation of GitHub. Once in a while, themers would start the dialogue anew, however it will at all times finish the identical. Importing a ZIP file was the one technique to submit a brand new theme or an replace to an present one.
Ultimately, these discussions included discuss of Git. Nonetheless, it appeared many of the ardour for integrating with any model management system (VCS) had waned. Most simply lived with the established order.
This has not essentially been a foul factor. Importing a ZIP has stored the method easy. Theme authors may use their most well-liked VCS (or none) and ship the ultimate product to WordPress.org.
As I seen the survey and thought it over, I modified positions. All through my historical past as a theme writer, I used to be clearly within the camp calling for VCS integration. I needed SVN (ultimately, GIT) entry to my tasks within the listing. Nonetheless, I had way back custom-made my development construct course of to include a ZIP creation step. The additional 30 seconds or in order that it took to add that file through the theme add kind didn’t appear to matter a lot anymore.
Just like the plurality of others who responded to the survey, I now want importing a ZIP file. Perhaps it’s what I’m accustomed to, however it will not have been my reply just a few years in the past. I’ve come to understand the simplicity of the present system.
Nonetheless, opening the theme add course of as much as different strategies ought to enhance issues for extra individuals. Specifically, I may think about theme retailers incorporating one thing much like 10up’s GitHub Motion for plugin deployment of their launch course of. Primarily, the Motion robotically sends an replace to WordPress.org’s SVN repository when tagging a launch.