> 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-7-url-aliases/url-redirects/exercise-7-3-breadcrumbs.md).

# Exercise 7.3: Breadcrumbs

Now that we’ve added a custom URL alias and all job postings inherit the common URL pattern, let’s link our breadcrumb to the URL alias and explore how we can improve the user interface by manipulating breadcrumb links.

In Unit 6 we created a View called *Job Posting* and added a link to the top Main Navigation menu ([Exercise 6.2](broken://pages/56s0d1WebMifLXLxoirT)).

![Image of Job posting View](/files/NlqwC14wUfZQom6ajMPT)

The *Breadcrumb* link **Job Postings** was added by GovCMS for you.

At the moment, when we access any of the **Job Posting** content, the *breadcrumb* does not show the link to the **Job Postings** page. This creates a UX problem as site visitors don’t have a visual guide of the site section they’re currently in:

![Image of Breadcrumb to Home](/files/hpEYXqe7DpEPROm0U6de)

We want to change the breadcrumbs so that when a **Job Posting** page is displayed, the *breadcrumb* shows the link to the parent **Jobs** page:

![Image of Breadcrumb to Jobs page](/files/KxsQDQGwxOKaxKciHt0r)

The *Breadcrumb* links are constructed from the URL of the current page and checking if the sub-path matches any page on the site. If it does, the system pulls the title of that page and creates a breadcrumb link.

Our parent page (**Jobs**) URL is **/job-postings** and our **Job Posting** *content* URL pattern is **/jobs/\[node:title]**. To get the **Jobs** page link added to the *breadcrumb*, all we have to do is to change its URL from /job-postings to /jobs. This way it will natively flow into the existing URL pattern for Job Posting content type and the link will be automatically generated in the breadcrumb.

1. Navigate to the **Structure** → **Views** and edit our *Job Postings* view.
2. Locate *Path* under *Page Settings* (middle top section).

   <figure><img src="/files/Hlwy4IDtVE2tHfWTqHfH" alt=""><figcaption></figcaption></figure>
3. Edit the *Path*, change it to **/jobs**.
4. **Save** the view
5. Test the *breadcrumb* by navigating to any *Job Posting* content. You should now get the **Job Posting** link in the breadcrumb.

![Image of Breadcrumb to Jobs page](/files/wScDICZ5amOpg8BlCEsK)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-7-url-aliases/url-redirects/exercise-7-3-breadcrumbs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
