Child Menu
When to Use This Component
USE CASES OR SCENARIOS
- Your page belongs to a larger section and has multiple sub-pages that users may need to access.
- You want to provide clear, intuitive navigation within multi-page content areas (e.g., admission information, policies, departmental sections).
- You are creating a structured “parent → child” page hierarchy and want users to remain oriented as they explore related information.
Component Do’s & Don’ts
There might be a time when you don’t know whether to use a Child Menu component or not. Here are some examples of how to effectively use a Child Menu component and when you shouldn’t use one:
DO
Use the Child Menu Block on parent pages that have multiple sub-pages to improve navigation, and regularly review your page hierarchy to ensure child pages are organized logically. Be sure to keep page titles concise and meaningful, as these titles will appear directly in the menu and help users quickly understand the content they can access.
DON’T
Don’t use the block on a page with no child pages, as this will create unnecessary empty space or confusion, and avoid creating child pages solely to force a menu—the site structure should reflect real content relationships rather than menu needs. Additionally, don’t use the Child Menu Block as a replacement for site-wide navigation, since it only applies to a specific section of the site.
Jump Links Menu block should not be used on the same page as a Child Menu block because both components serve a navigational purpose. Jump links rely on in-page anchors, while child menus are designed to reflect site structure and page relationships. Combining the two can lead to inconsistent navigation behavior and accessibility challenges (such as unclear focus order for keyboard and screen-reader users).