> 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-4-taxonomy-categorising-content/taxonomy-categorising-content/exercise-4-2-add-taxonomy-field-to-content-types.md).
# Exercise 4.2: Add Taxonomy field to content types
Use your experience from the previous exercises to add the State/Territory field to the Job Posting content type.
{% hint style="success" %}
**Hint** - use Entity Reference for the field type or Select lsit if you prefer a dropdown. Follow the screenshots below if needed to configure the field correctly for the *Job posting* content type
{% endhint %}
In the **Manage form display** of your Job content type, you can set **Select list** as the field widget type as shown below.
Showing Select list field widget for State
When creating you Job content, the state field will look similar to the following screenshot.
Showing the State field on the job creation page
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://salsa-digital.gitbook.io/govcms-site-builder/unit-4-taxonomy-categorising-content/taxonomy-categorising-content/exercise-4-2-add-taxonomy-field-to-content-types.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 `build a script that syncs our docs to a CMS` 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.
