If I get time, I'd like to take a crack at recipe building. I envision a spreadsheet style list, with annotations and instructions.
The "linking" facility was designed in part to make recipe-making as brainless as possible -- in fact, obviating the need for the "recpie" concept altogether. (For a new user to be able to e.g. use an ns_kit dbkit, the instructions would be as simple as: 1. download nskit.dbkit; 2. download the samples from nskit.com; 3. launch doggiebox and point it the samples when it asks; 4. enjoy.)
Are there other aspects of by the recipe concept that are not addressed well by this approach?
I had never thought about it before, but it seems that most of the things I describe here would travel with the dbkit file. If this is true, the linking is all that is needed. If it's not then... Most significantly, panning and volume settings are hardly ever set to the default "center" and "100 percent" for each drum. As if that weren't enough, new users should still receive some "recipe" instructions about the general kit setup in terms of drum type and variant. This has a big effect on the usability of the final kit. Also, icons are, in my opinion, a significant aspect of usability that should probably not be overlooked.