> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-content-administration/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-content-administration/taxonomy/creating-new-terms.md).

# Creating new terms

{% hint style="info" %}
You should only create new taxonomy terms if your internal governance allows it. Having too many taxonomy terms can make things more difficult to manage.

For example, if you had the taxonomy term for *each year* of the annual report, then each term would only apply to one or two pieces of content. Whereas a more general term of **Annual report** that applied to all annual report content would be more useful.
{% endhint %}

### View vocabularies and taxonomy terms

To see the list of vocabularies available to use on a website, go to **Structure** and then **Taxonomy**.

<figure><img src="/files/neW8iw40TFV7FYlQ8ltu" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Taxonomies are highly customised and your website will have different vocabularies.
{% endhint %}

### Adding a vocabulary

From the **Taxonomy landing page**, select the blue **Add vocabulary** button at the top.

Provide a **Name** and a **Description** and select **Save**.

<figure><img src="/files/1kcZeV4c3VcoNjL9j8FE" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}
While Content Authors can create new vocabularies, implementing them in a meaningful way requires a developer.
{% endhint %}

### Adding a taxonomy term

1. Select the **List terms** button associated with the **Vocabulary** you want to add terms to

<figure><img src="/files/LCHBSeEIIx6AdqTeWL9q" alt="" width="563"><figcaption></figcaption></figure>

2. At the top of the page select the **Add term** button
3. On the next screen you'll be asked to enter in the following information
   1. **Name**: The display name for this term
   2. **Description**. Optional, a short description about the term
   3. **Relations**: Allows you to set a parent term and weight, however both can be set on the **Vocabulary page** using the 4-arrow widget, like the menu items
   4. **Revision information**: You can include revision information when editing a term, similar to the revision information in basic content
   5. **URL alias**: Some websites allow taxonomy terms to be accessed directly as landing pages - leave this blank to use the default URL alias pattern set by your developers
4. Select either the **Save** button to add the term and remain on the form to add more terms, or select **Save and go to list** to add the term and return to the **Vocabulary page**.

{% hint style="info" %}
Content types can be configured by your developers to allow you to add new taxonomy terms on the fly when editing content. It's important to always check your spelling when creating new terms this way, as any spelling mistake will simply create a new term.

If an existing term used on your website is **Reports**, and you type in the taxonomy term of **Report**, a new term will be created that no other piece of content on the website will have.
{% endhint %}


---

# 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-content-administration/taxonomy/creating-new-terms.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.