An example of what I'd like to see is the recent code improvement for CTCSS. The previous implementation wasn't much of an improvement from the original manufacturer code. The new code is much better. I still have no idea what 'inner' and 'outer' CTCSS is and I've been doing this radio thing for quite a while now. The new code abstracts this, makes the function simple to use, as it should.
The existing examples are good but could be a bit more functional. The content that is missing doesn't stop us from making progress, it just takes longer. Instead of seeing how to implement a feature, we have to paw through the library manually to find each function in order to then test it. It would be nice to see each supported feature (CTCSS, transmit, receive, etc.) get documentation like a wiki page. A good comparison would be how each item or element in minecraft gets its own wiki page. Could be tedious to make for an individual but if it were in wiki format, the fledgling community could begin work on it and make a huge dent in the overall task. I don't want to sound like a whiner but the learning curve is somewhat steep for the masses at this point. If the hamshield had a wiki like minecraft, it would ease up on the slope of that curve and from there, I think that this would take off.