Introduction to SharePoint information architecture
Well-planned and executed information architecture is a prerequisite for an intelligent and high-performing intranet, hub, or site. The most important first step in planning an effective information architecture is understanding your users and helping them find what they need to complete tasks in a way that makes the most sense to them.
Information architecture also helps improve user adoption, satisfaction, and productivity while reducing IT costs, information overload, and minimize compliance and security risks.
Note
All navigation types (site, hub, global, and footer) are limited to 500 child links at each level. Additional nodes added after the limit has been reached will receive an error.
In this article:
- Learn the main elements of information architecture
- Review the different roles involved in implementing information architecture
- Understand the different levels of information architecture – global, hub, and local
- Explore SharePoint information architecture building blocks
Information architecture elements in SharePoint
Information architecture is about how you organize and label your content and how your visitors interact with the content to get work done. On websites, information architecture includes elements like navigation, search, site hierarchy, taxonomy, and security. Modern SharePoint information architecture is also about how to ensure the right content gets to the right people and follows your organization’s content compliance regulations.
Information architecture covers six main elements that relate to way finding in SharePoint:
- Global navigational structure – Considered the top level of navigation across your SharePoint tenant and how you structure your sites so that users can find content including the home site of your intranet.
- Hub structure and organization – Hubs enable you to group together similar topics, tasks, and content.
- Local site and page navigational structure – How content is organized on each site and page so that users can further navigate or consume content effectively.
- Metadata architecture – Metadata impacts search and browsing structure as well as compliance and retention policies.
- Search experiences – How your users "consume" information architecture in addition to browsing.
- Personalized content experiences – How specific content is targeted to certain users and groups of users.
Designing the optimal structure for hubs, sites, and pages requires sufficient planning. It also requires knowledge of the domain, content, understanding the user experience, awareness of design approaches, and best practices in Microsoft SharePoint. Even with a good plan, information architecture is a continuous process. Over time, organizations change, people change, and projects change. Over time you'll learn about your users, which will allow for adjustments that make content more discoverable.
Understand your role and how to collaborate
Information architecture for your organization is most effective when many types of roles collaborate on your intranet, such as: intranet owners, departmental business owners, IT administrators, and hub owners just to name a few. Learn more about how each role plays a part in planning, implementing, and managing ongoing maintenance for organizational information architecture.
Organization intranet owner(s) – The organizational intranet owners consist of a mix of decision-makers and job functions to manage the overall direction and coordination of your organization's intranet. Organizational intranet owners work with business owners (departments) and IT admins to establish global and hub level navigation. Organizational intranet owners spend most of their time working on planning and implementing global and hub level navigation.
Departmental business owners – Departmental business owners represent large areas of the organization, like human resources, marketing, and engineering. Departmental business owners work with organizational intranet owners to ensure their area of the business is well-represented in global and hub navigation. Departmental business owners should be included early in the planning stage to ensure business and user needs are met.
IT Admins – IT admins partner with organizational intranet owners and departmental business owners to implement high level navigational structure like implementing the start page and hubs. IT admins also help implement certain governance policies around site creation and usage. IT admins are involved in planning, implementing, and maintaining information architecture as the business changes and scales.
Hub owners – Hub owners manage hub-level content, branding, permissions, and navigational elements for hubs in your organization’s intranet. Hub owners partner with departmental business owners and IT admins to plan, create, and manage hubs throughout the lifecycle of your organization’s intranet architecture.
Site owners – Site owners manage site-level content, branding, permissions, and navigation. Depending on the needs of the business and users, site owners can associate their sites to hubs if the hub owner allows.
Content creators – Content creators are responsible for keeping site content updated and publishing news. Content creators should be given a site member permission level to make changes to sites and pages. Content creators partner with site owners during the implementation and management stages.
Content consumers – Content consumers aren't represented in the counts as anyone who is using and viewing content throughout the three levels of navigation. Intranet owners, departmental business owners, hub owners, and site owners should regularly engage with content consumer – especially during the planning process – to ensure the right content is findable and usable.
Guiding principle: the world is flat
Classic SharePoint architecture is typically built using a hierarchical system of site collections and subsites, with inherited navigation, permissions, and site designs. Once built, this structure can be inflexible and difficult to maintain. In the modern SharePoint experience, subsites aren't recommended. In the new "flat" world of modern SharePoint, plan to create one site for each discrete topic, task, or unit of work. This allows you to easily distribute management and accountability for each content collection and support your ability to move sites around in your navigational architecture without breaking links. Moreover, when a topic is no longer needed, you can easily archive or delete a site with minimal impact.
In the new flat world, you have several ways to connect sites and content to each other as part of your information architecture toolkit:
- Use "roll up" web parts such as News, Highlighted content, or Sites to dynamically surface content from other sites in an existing site.
- Use inline hyperlinks to provide more detail about a topic to provide more information to your reader (as demonstrated in the previous bullet).
- Add explicit links to related sites in your site navigation.
- Connect families of related sites using hubs.
Levels of navigation
There are three levels of navigation to think about for modern SharePoint experiences:
- Global navigation for the entire collection of sites that comprise your intranet
- Hub navigation for groups of related sites
- Local navigation of an individual site
Global navigation
Many intranets include top navigation that persists on every site. Global navigation allows you to create an overall navigation story for your intranet that visually connects all the sites, content, and tools your viewers need to get work done. Every organization has a different requirement for what goes in global navigation, but some of the category labels often used include concepts such as:
- Home
- About Us
- News
- Working Here/Work Resources/Administrative Services/Administration
- Operations/Operations Services
- Pay & Benefits
- Life & Career
- Locations
- Policies & Procedures/Tools & Resources/Safety & Security
The goal of global navigation is to support browsing to content. Since there's limited real estate available for global navigation links, global links generally point to major category navigation pages, sub-links, or a mega menu experience to provide enough information to help viewers find the content they need. Because the context for global navigation must be broad, it's challenging to make the labels both comprehensive and useful. If you plan to implement global navigation, you want to test your proposed navigation to make sure that it resonates with users.
Global navigation is enabled with the SharePoint app bar on your home site. You need to have a home site to enable global navigation. Global navigation appears on the left side of every site and page.
Hub navigation
SharePoint hubs help organize related sites based on project, department, division, region, or concept. Hubs make it easier to discover related content such as news and other site activities, apply common navigation, branding, site structure across associated sites and search across all associated sites. One of the important planning decisions for hubs is planning the hub navigation.
Hub navigation appears above the local navigation on each site, just below the suite bar, as shown in the image earlier in this article. Hub navigation is established in the site that is declared to be the hub. It's defined by the hub owner and is shared by all the associated sites.
Each site can belong to only one hub at a time, but you can associate hubs together in a combination of navigation links and associated hubs as part of your navigation experience. For more information, see Planning your SharePoint hubs.
Local navigation
Local navigation is the static navigation that viewers see on every page of your site. For team sites, local navigation shows up on the left side of the page in the area referred to as the "quick launch". For communication sites, local navigation shows up at the top of the page. Local navigation is on every page in your site. It creates a persistent experience to allow site visitors to move back and forth among the pages and content on each site. Think about how viewers might explore your content and use local navigation to support that exploration.
Example: A travel site might have the following local navigation links that support viewers who are exploring the travel site from the perspective of "what am I allowed to do?" and viewers who are exploring the travel site from the perspective of the travel process – before, during, and after their trip.
- Travel guidelines
- Air
- Car
- Ground transportation
- Hotel
- Train
- Before you go
- Travel approval
- Booking service
- During your trip
- Travel safety
- Itinerary changes
- After you return
- Expense reporting
- Trip reports
Where you see local navigation elements:
Team site navigation
Communication site navigation
Sites
Your intranet and portals are comprised of team sites and communication sites that provide further access into the site’s pages, lists, and libraries.
One component to modern SharePoint team sites that makes information architecture easier to implement and maintain are Microsoft 365 groups. Microsoft 365 groups provide a membership service that allows for easy hub and site permissions as well as other functionality for SharePoint team sites and Microsoft Teams. With Microsoft 365 groups, you can give a group of people access to a collection of collaboration resources like Planner, OneNote, SharePoint team sites, and more. Microsoft 365 groups can only be used on SharePoint team sites.
Pages
Pages within team or communication sites provide an opportunity to use dynamic web parts that automatically update content from other sites and pages like News, Highlighted content, or Sites web parts. Every page in each site tells a story for the reader.
Your sites generally include three types of pages:
- The home page where you provide an overview of your content and introduce the reader to what they find on the site.
- Navigation pages that provide options or summary information for the reader and help them get to a decision point about where they want to go next.
- Destination pages that are the end point of the reader’s journey. This is where you'll present information to read, print, or download. If you have a lot of information on your destination page or you want to provide supplemental explanations for detailed topics, you can create an ancillary page.
Since we know that most readers don't read every word on a web page or even scroll to the bottom, you need to pay attention to how you present information on each page. Make sure that you put the most important information – the information that your readers must have for your communication to be successful – at the top of the page. As the page continues, you can add additional information that is helpful, but not crucial. Think of this as writing with your summary or conclusion up front, instead of at the end. Use sections, headings, and bullets to make your pages easier to read. For more info, see Add sections and columns on SharePoint modern page.
Navigational elements
Navigational elements are menu styles like the mega menu, cascade menu, and footer menus. Secondary navigational elements include inline links and buttons.
Personalization elements
Audience targeting - Audience targeting helps the most relevant content get to the right audiences. By enabling audience targeting, specific content is prioritized to specific audiences through SharePoint web parts, page libraries, and navigational links.
Information barriers - Information barriers are policies in Microsoft 365 that a compliance admin can configure to prevent users from communicating and collaborating with each other. This is useful if, for example, one division is handling information that shouldn't be shared with specific other divisions, or a division needs to be prevented, or isolated, from collaborating with all users outside of the division. Information barriers are often used in highly regulated industries and those with compliance requirements, such as finance, legal, and government.
Multilingual considerations - If your organization spans a diverse population, you may want to make content in your intranet sites available in multiple languages. User interface elements like site navigation, site title, and site description can be shown in the user's preferred language. Additionally, you can provide pages and news posts on communication sites that you translate and that are shown in the user's preferred language.
To show the site name, navigation, and footer of your site in the different languages you've made available, each must be translated manually. For example, let's say you've created a communication site with an English default language, and you've enabled the site for Spanish and German languages. When you create a site, you set up the site name and description in the default language (in this case, English). You can also update the site name and description after site creation. Then you create the navigation nodes and footer content in English.
After the site is set up in English, a user with Spanish as their preferred personal language manually edits and translates the title, description, navigation, and footer content into Spanish. A user with German as their preferred personal language does the same for German. Once the content is translated, it displays for all users of those preferred languages.
Metadata architecture
Columns and content types are the two most important metadata elements that you can use to organize documents and pages in your SharePoint site. Metadata helps your users filter and sort content within a list or library – but also helps with search. Use columns in your Site Pages library as well so that you can use highlighted content web parts to dynamically connect related pages based on shared metadata.
Folders are another way to organize document content, but folders are a physical construct with limited flexibility. Folders aren't necessarily bad – they can help you manage performance and security in your document libraries – but folder structures with more than one or two levels of nesting create a significant discoverability burden for users and should be avoided. Every site comes with one document library – but you aren't limited to just one library. Instead of using the one default Documents library on your intranet sites, consider adding topic-specific libraries and add site columns to organize your content within the libraries to avoid creating multiple levels of nested folders.
Search experiences
Search uses your information architecture investments to help users find content when they don’t know where it might be in your architecture. It also helps users discover content that they may not have known about.
You can help users discover content and improve search outcomes by using several features in search, including acronyms, bookmarks, Q&A, floor plans, and locations. For more info, see Make content easy to find and Search experiences in SharePoint.
Next: learn about SharePoint information architecture principles