Agreed on the Staff Picks as well as the Community Picks. Although at times, when I am looking at “reviews” of equipment, I will read where someone says well I don’t think it does X, when it clearly states that it does do X (i.e. person thinks a monitor doesn’t have tilt, yet it states in the specs that it has 5 to 15 degrees of tilt, lol just read this at Egghead). Which leads to, how about as another poster has stated, that the Bill of Materials state if there is PDF/Text/Http Links for Documentation. If this is done, I would suggest, that the documentation, contain a usage section on how the submitter expects the content to be used (i.e. BluePrints), and the steps that would need to be done, in order to achieve those goals. Now this would be something that Epic as vetting would simplify their life to an extent, they have the roadmap, does the blueprint do it or not?
In terms of sounds/graphics/content, that comes down in a lot of ways to each person’s “pleasure” and is very hard to be empirical about something so subjective. But if we were to look at “sound affects” I would think it would be reasonable to state how long each “sound” is, and is it designed to loop seamlessly (I believe someone already mentioned this concerned FX).
Just my thoughts.