> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-site-builder/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-site-builder/unit-1-functional-analysis/1.6-site-navigation.md).

# Site navigation

Menus are a collection of links (menu items) used to navigate a website. The core Menu UI module provides an interface to control and customise the menu system. Menus are primarily displayed as a hierarchical list of links. By default, new menu items are placed inside a built-in menu labelled **Main navigation**, but administrators can also create custom menus.

The GovCMS installation profile contains five menus:

1. **Administration** (administrative task links)
2. **Footer** (site information links)
3. **Main navigation** (site section links)
4. **Tools** (user tool links, often added by modules)
5. **User account menu** (links related to the active user account)

You can customise menus in the menu administration functionality by:

* Creating new custom menus
* Adding new menu items
* Reordering menu items by setting their "weight" or by dragging them into place
* Renaming menu items
* Changing the link title (the tooltip that appears when you mouse over a menu item)
* Moving a menu item into a different menu by editing its Parent property

A menu item will only be shown to a visitor if they have the rights to view the page it links to. For example, the admin menu item is not shown to visitors who are not logged in.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-1-functional-analysis/1.6-site-navigation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.