My goal, simply, is to be able to populate the drop-down list associated with
a fly-out with any item ,object, URl, etc. that could appear in a QuickLaunch
display, and to control this for each sub-site (several levels deep) without
regard to inheritance or parent object settings.
My experiment today contradicts advice given from this group, no "publishing
site" was required.
I had a brand new, out-of-the-box, MS team template site put up. The first
thing I did was to activate *all* site collection features. Next, I built a 3
level deep sub-site structure based on team/collaberation templates. Lo &
behold, fly-outs were available on all sub-site structures via the "look &
feel" Navagation link. I had not seen this link previously on my team sites in
our company's PROD environment.
BUT
1) the fly-outs only picked up sub-sites, not DocLibs, plain WEB pages, lists,
etc.
2) the fly-outs were *not* availabe on the top-level site.
This was all thru the GUI, not SPD.
Comments or suggestions for next experiment please.