I think what I meant to say is that for folks new to dnn it's nice to have a choice of recent earlier versions available only because there is usually a lot of user history with them and can make development a little faster and less frustrating.  Many others have already cut the path and offered code, fixes, examples, etc., either through forum post, blogs, or other means.  When I was first getting started, modules with too many features just simply overwhelmed me.  Anything simple got used and as I enjoyed more success I started to appreciate the additional features found in modules.  Good to hear though that the upgrade path should be smooth from version to version.  Keep up the good work.

Paul

Thanks again Paul.  You bring up a good point, and it is actually one of the reasons for the new template type.  I have had a lot of requests for specific kinds of menus and special tricks.  Sometimes I would add in another setting and make it available to everyone, and sometimes I would do a custom build for people.

As time went on, the module started getting a lot properties that could be set, which in turn would confuse people new to using it.  I also started having more and more requests for custom builds and they were getting hard to mange.  So I thought... what I need is a way to capture all these specific types of menus in their own self-contained configuration. To some extent that can be done with a sample skin, but I also get requests for changing the actual output so that CSS class names are different, ID's are added, etc. etc.

Anyway to make a long story...ummm..  longer.  That is when I got the idea to make a templated nav system so that all output would be completely customizable and self-contained. You can even change the heirarchy of the output, or create several templates and "wire" them together with javascript that gets correctly linked to at the head of the page.

Now people can share templates, or I can create more types of menus, or skin developers can have more choices for navigation that they can build right into their designs.

I do hear what you are saying about meeting simple needs first and building from there though.  I think some of the best modules have started out simple and have been continually enhanced along the way. Hopefully the Snapsis CSS NavMenu is not too over-whelming for first time users, but I'll do my best to simplify things for anone that asks. 

If you have any other ideas about how to best achieve these goals I'd be glad to hear them.