Hi guys, I just wake up OK, just a brief of the review process.
1) Review the live preview to check the design, features ( also read the item descriptions )
(a) The design is good enough, proceed to the files testing, localhost testing.
(b) The design is not very good but it offers some unique features, proceed to the files testing, localhost testing – may advice the author to improve the design and re-submit. We’d love to see more unique design / features / approaches in a theme, so, we will encourage the author to improve it.
3) I seldom use the sample data from the author but I will add content manually. Some of the themes are using custom post type which required different type of data and testing.
4) Test all the custom options, widgets, functions and features and make sure it works as described.
5) Read through the documentation file. This is tricky, some authors provide > 100 pages instruction and you wont expect we read all that. So, we just scan through the content and see whether he cover the main features setup.
(a) I will check the files ( codes ) and see how it works. Some authors provide a very flexible option where the user do not have to touch the code to edit anything. For example the 3 columns data, slider’s content ( can add and remove – ajax ) etc ) – This is also a reason to increase the price.
(b) Some authors provide good (unique) features but it required manual setup, for example the user need to copy a bunch of codes and paste to somewhere, or they need to upload images to certain folders and change some codes to make the slider works properly.
6) If everything oK, I will check some key files to and make sure it works and do not contain any self promotion content ( from other theme club or website ).I think this is pretty much of it.
Thanks Kai! You gave great details and it really put my curiosity to rest….
To be honest, I can’t remember the last time I ran into a situation when reviewing a WP theme that I needed to run it locally with pre-populated post data.
Then, how do you test custom options admin panel set-up by the theme? It seems to me that these options are very important, at least to determine the price.
Or am I wrong?And how do you test data import?
I think if they’re checking the design first and it doesn’t pass, then they won’t bother with the theme admin panel or anything else. But if the design rocks, I’m sure they take a peak at everything under the hood to determine the price. That’s just an educated guess though.
Great insight! Thanks! So what do you do if there isn’t a live preview for a Wordpress theme? Isn’t it difficult to gauge a theme if there isn’t content behind it with the appropriate structure? Do you guys go so far as read the theme’s instructions to see how to add image to the slider or designate thumbnail images for posts?
I suspect this topic has been brought up before but I’m curious to know how submitted Wordpress theme files get reviewed. Specifically what I mean is if there’s a particular order of the files that they go through? Do they load the theme into their own local host with a pre-made XML data file? Or do they go directly to a live version if provided by the author? Or maybe the way the files are reviewed depends on the style of the reviewer. One reviewer checks out the code first and then loads up the design in their localhost and another only views in localhost.
Does anyone have any idea how the process works?
It’s really just to satisfy my own curiosity.