A brand-new user's first add-on should be the template from the Tutorial that we have. It should probably be heavily document about why each part exists. This lets a user start with an add-on that already works, and then they can just configure it to do something different or more. It's very powerful to be able to create a new addon, and immediately click Test and watch it work. See http://www.youtube.com/watch?v=NaFW4zguoZk for the point-of-view of a new add-on developer.
Arron is presently coding an admin page that will allow super-users to mark add-ons and libs with "example" and "featured". Perhaps for the first add-on the user ever creates we should throw up a modal and let them choose which type of example to load?
fixed on master https://github.com/seanmonstar/FlightDeck/commit/14fef29dbb856b21bbfd3270b4d0cceed7d980e8