> 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-6-content-listing-with-views/related-content-by-term/exercise-6-5-make-a-list-of-states-territories-block.md).
# Exercise 6.5: Make a list of States/Territories block
In this exercise we’ll add a list of the **States and Territories** in the sidebar, so the page looks like the screenshot below.
States Block in sidebar
1. Go to **Structure** → **Views**. Click **+ Add new View**. Add in these settings:
* **View name:** States/Territories.
* Select to enable **Description**: A list of State and Territory terms.
* Show *Taxonomy* terms of type *State/Territory* sorted by *Unsorted*.
* Select **Create a block**.
* **Block title**: States/Territories.
* **Display format**: *HTML list* of *Fields*.
* **Items per block**: 0.
* **Use a pager**: Leave unselected.
* Click **Save and edit**.
2. Go to Structure → Block Layout.
3. In the *Sidebar* area click the **Place block** button.
4. Find **States/Territories** block in **Lists (Views)** category and click the **Place block** button.
5. Configure block visibility settings to only display it on the **Job Posting** *content type*.
6. Click **Save block**.
7. Scroll down and click **Save Blocks** to complete.
8. Navigate to a *Job posting* content page and locate your block.
---
# 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-6-content-listing-with-views/related-content-by-term/exercise-6-5-make-a-list-of-states-territories-block.md?ask=&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.
