I am not trying to be contradictory, but you must understand, my largest problem with DotNetNuke is its lack of adequate documentation.  The reason why I find it to be a problem is when things go wrong the documentation is the only real way to fix and understand the proble.  This prompts my next question.  Mind giving me a page citation as to where you found the Module Developers stating that the Key of one item must be empty.  Page 20 shows how to add the controls and it shows one being empty but doesn't explain that it is "REQUIRED".  That is not a clear way to document a required item.  From Page 58 on it explains the Definition file but makes no mention of one key being required to be blank.  The last time the documentation was updated was 2005 according the the last page.  The only reson I was able to figure out the problem I was having was because of this post. The search function for the Forums is so terrible that I was extremely lucky to find this post.  Again, as I stated before, this information is not in the documentation, unless you can provide the page that states it is required on.  To put something in there and assume we will understand it is required is truly not a good way to document something that will stop custom built modules from functioning.  This really needs to be in the documentation. 

Let me know where to send it.  I have a large collection that I keep in a series of blogs on my website.  I also routinely try to respond to forum posts here.  As for you not liking my criticism, I am not talking about an "OPTIONAL" part to module development.  I am talking about "REQUIRED" items.  On top of that I have no problem with someone informing me that there is a problem with something I work on.  I figure that is the way software becomes better and products survive problems in its design.  I often find myself trying to figure something out and asking myself why this isn't in the documentation.  I am surprised that this doesn't occur seeing as how many of the developers use their own products.  If you don't like criticism then don't do anything because someone will always have something to say. 
     Also, I realize it doesn't indicate that I have to have a value on all keys, I prefer to do so as it makes it clear to someone else working with me.  I don't do all the work on my own and I prefer to have all things labeled so transitions and other contributions are easily able to be understood. 
     Finally,  if you would like me to contribute you might want to either 1.  Let me know how 2.  Put the information in an easily accessible place on the website or 3.  Provide more information on how.  I work for a living and don't have days and weeks to search for how, so if you can't provide that information then don't suggest it.   If you add it to the website then make it obvious because the search function on the website returns terrible results and I won't be able to find it otherwise.  I would be glad to contribute, and I routinely try to do so in the forums.  I DotNetNuke is wonderful, but also has some problems.  Seeing as how nothing is perfect then that is to be expected.