
Building a Custom Global
Navigation Solution
In SharePoint, every site collection has its own unique navigation structure. This can be desir-
able when each site collection is a distinct entity, but many times, it can be desirable to share
navigation across site collections. This chapter uses a ctional company, ACME Corp, to help
illustrate reasons why a global navigation solution might be implemented and to provide a set
of requirements that the solution must deliver.
ACME Corp is a large, ctitious, multinational company that utilizes SharePoint 2010 for its
intranet. Like many large companies, ACME’s intranet is split into a number of different site
collections. As is typical for many information architectures, the site collections have been cre-
ated less because the content is truly meant to be separated and more to keep content database
sizes manageable. ACME wants to share a standardized navigation menu across multiple site
collections. The rest of this chapter is devoted to implementing such a solution.
The code for the solution created in this chapter is available for download
at the book’s companion Web site,
www.wrox.com.
DEFINING THE REQUIREMENTS
Any navigation menu solution is expected to support certain basic functionality, such as the capa-
bility to display a hierarchal list of ordered links that supports an unlimited depth. In addition to
standard menu functionalit ...