
I’m on the last day of my team meetup in Auckland, New Zealand. This is the view from the balcony off my bedroom.

I’m on the last day of my team meetup in Auckland, New Zealand. This is the view from the balcony off my bedroom.
If we tell people that they don’t need to be expert developers to review themes, and that this is a good way to learn better coding practices, why don’t we do the same with design? Good design is just as subjective as code standards (in that the basics aren’t, but people like to argue about it anyway).
The quality of code in the theme repo is improved by the review process, so we should encourage design reviews to increase the quality of design, too.
Some suggestions: fill out the design guidelines in the theme review handbook (maybe with a “how to give feedback” section), then encourage designers to review themes, without worrying about doing the full code review - not all designers are or want to be developers. Publicize that this is something people can do, and it’s still contributing. Encourage people who might not be comfortable with giving design feedback to “self-report” a usability test- write out what they were thinking while activating & setting up a theme.
Mel & I have been talking about “doing some nature” basically all summer— whether that was going to a beach, or taking a hike, or kayaking… and it never happened. To be fair, between WordCamps and other conferences, meetups, and work, summer was pretty busy.
Now that it’s fall, and the conference circuit is slowing down (well, there’s another WordCamp this weekend…), we’re trying to do some of those things we didn’t do this summer. So we took the day and went up to the Middlesex Fells Reservation (what a trip, maybe we’ll get a car next time).
We probably hit at least 6 of the labeled trails, and 2 roads, trying to make our way from Oak Grove to the reservation headquarters at Spot Pond. It ended up being about 6 miles of walking through the woods, along rocky trails & brooks. We had lunch at the boat rental place (closed for the season, but had picnic tables) at the edge of Spot Pond. And then took a much shorter rout to a different entrance, so we could catch the bus home.
A few months ago I had the idea of creating a wp-cli command for the theme check plugin, and integrating that in with Grunt so that I could use it in my theme build process.
Yesterday I sat down and pulled everything together to do just that.
I’ve modified the existing Theme Check plugin to include a WP-CLI command, and you can grab it on github. If you’re interested, you can also check out the changes I made to create this (as some work had to be done on the plugin directly).
Once you have that version of Theme Check, and can run
wp theme review check <theme-name>
you can also pull down the grunt plugin that integrates with it. Grunt-wp-theme-check is on github and npmjs, and the readme should do a decent job explaining how to use it. Use the following to install it for your project:
npm install grunt-wp-theme-check --save-dev
If you’re still a little lost, you can check out my updated Grunt-Theme-Builder, which explains my process for building and packaging themes. Note that this is just a Gruntfile and package.json, if you want to use it, you’ll need to set up your theme files like I outline, or just copy-paste the tasks you want.
Let me know if you’re using it and if you run into any issues :)