I am in a process of gathering requirements of a portal based on multiple departments using SharePoint 2010 Enterprise.

I've noticed on some portals where there is a top bar and a tab called "Organization" when you click on it opens sub menus with a list of departments and it the department has more sub departments then it should slide right also.

How to achieve this functionality or suggest me some good menu resources so i can incorporate in my portal and give a professional look.


2 Answers 2


You have lots of options here! Take a look at the Navigation section on MSDN to gain further info on whats possible out of box.

The navigation in SharePoint (both SP2010 and MOSS) are based on the ASP.NET sitemap provider model with a custom navigation control. As long as you keep your site in one site collection this works fine, but as soon as your architecture demands that content should be split up between site collections the OOB navigation comes up short and you need to rethink your navigation strategy. Theres alot of stuff out there on this, but start here, here and here.

Also consider if the left navigation in SharePoint is appropriate. This is usually the first standard component to get disabled, as it is really not that usable especially for internet facing sites.


The top tabs, left navigation and breadcrumbs are all built on the ASP.NET Navigation API. This uses a provider architecture - providers give you the model (Tree of SiteMapNodes) for the site, and navigation controls, such as the SiteMapPath web control (used for breadcrumbs in SP2007), which render that model in a way the user can use.

SharePoint ships with it's own controls for both parts - providing models and display - though it also uses standard ASP ones.

Probably your best bet is to check the web.config for your web application - this will have section in it that details the navigation providers that SharePoint comes with preconfigured in the section. The names of these providers will be shown in your pages as data sources for your navigation controls.

If you're using Enterprise, the big thing to note is that some of the navigation providers will use the publishing features. To support publishing pages, these display quite a different model - but that model can include Publishing pages and is generally a bit easier to configure to display a useful navigation structure dynamically. It does, however, lack some of the features of the 'normal' team site navigation, such as the Portal Site Map connection.

You can add your own configurations of the providers to Web.config, but be sure to do it via an SPWebConfigModification.

You can also control how your navigation appears by controlling things like if the left or top navigation shows 'fly out' menus, what's shown in the breadcrumbs, etc.. To make these changes, you'd probably create a new master page, or possibly change your specific ASPX page for your site.

Finally, you can write your own navigation providers (or new providers, if you write one), or navigation controls. It doesn't necessarily have to be a complicated thing to do, and can be quite useful! I did one for a case management system a while back that provided 'related cases', and this was convenient as I could easily plug it into existing navigation controls to display it consistently with other navigation in the site.

You may find this useful: http://www.novolocus.com/tag/navigation/

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.