Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

How to make sub-site navigation bar on a publishing portal?

  Asked By: Jay    Date: Jan 31    Category: MOSS    Views: 2437

I'm trying to build a masterpage for our intranet sub-sites.

Each subsite should have the same global navigation. This we're creating
from a list kept at the top-level site and displayed via custom XSL in a
dataview web part.

Each subsite should then have its own 'subsite' navigation bar on the
right side of the page.

At first, I thought we'd just use the quick-launch bar, as that's built
in and really provides the navigation for an individual site.

Alas, from what I can tell, if we're building publishing sites, the
quicklaunch bar isn't site-centric, but rather just mimics the default
top-tab navigation site-wide. In otherwords, if I make a publishing
sub-site, the quicklaunch bar has links to all of the other subsites in
the portal, rather than just links within the sub-site itself.

Is that a correct observation?

It appears that I could just make the sub-sites team sites, as for
whatever reason, team sites' quick-launch bars ARE site-centric--but
then I lose the ability to create template pages for authors to use.

At this point, the only think I can think of is to create yet-another
custom list on every subsite and use the dataview web part once again to
create our own custom navbar. Not a huge deal, but if anyone has a
better idea, PLEASE let me know! I'm at the point where every single
feature on our intranet is feeling more and more like a giant hack,
rather than a pragmatic solution leveraging what few cool features there
are in MOSS's CMS feature set.

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Christen Roberson     Answered On: Jan 31

All the navigation  bars in SharePoint are using SiteMapProviders or
things that inherit from SiteMapProviders as the datasource. You can
create your own navigation control to use the built in providers (with
custom filtering) or create  your own custom  SiteMapProvider, add it to
the Web.config and point  the navigation controls at it.

 
Answer #2    Answered By: Faith Delgado     Answered On: Jan 31

> All the navigation  bars in SharePoint are using SiteMapProviders or
> things that inherit from SiteMapProviders as the datasource. You can
create  your own navigation control to use the built in providers (with
custom  filtering) or create your own custom SiteMapProvider, add it to
> the Web.config and point  the navigation controls at it.

But there's nothing out-of-the-box to modify and maintain said sitemap
files, correct? Or is there? Can a siteMapProvider source data from a
MOSS list?

Plus, well, that likely won't work as I'd also have to build  a custom
navigation bar, as the HTML/CSS isn't what we want either.

 
Answer #3    Answered By: Amrita Durgude     Answered On: Jan 31

Although there is nothing out of the box, you could build  your own
SiteMapProvider that uses pretty much anything you want as a backend,
including a SharePoint List. And No you wouldn't have to build a custom
Navigation bar. That's the point. the Navigation Bar, QuickLaunch Bar,
and Breadcrumb trails are all bound to Versions of a SiteMapProvider
object at runtime. All you need to do is create  an equivalent
SiteMapProvider, put it into the Web.config and set the appropriate
existing Nav control to use your provider.

 
Answer #4    Answered By: Maricela Conway     Answered On: Jan 31

In publishing  sites, the "quick launch" is referred to as
the "current navigation". There is an option available in the
navigation settings screen for the site  owner to configure whether
it displays links  from the parent site, or from sibling sites, or
just for the current site.

 




Tagged: