> 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-8-site-building-exercises/extend-content-types-with-new-fields/exercise-8-1-add-an-external-link-field.md).

# Exercise 8.1: Add an external link field

In this exercise we’ll add a new link field to the *Job Posting* content type. The link will go to “More information” on another website.

## Add the link field

1. Go to *Structure* → *Content types* → **Job Posting** and click on the **Manage fields** tab.
2. Add a new field and use the following settings:

   <img src="/files/Y8JqZxvnxnHdgzY6xhcp" alt="Image of new Field settings" data-size="original">
3. Click **Save and continue.** This will take you to the Field settings page.
4. There are no changes so just click **Save settings**.
5. This takes you to the settings for this field on the *Job posting* content type.

## Test it

Go to a Job posting and search for the 'More information' section and **Link** field.

![Image of new Field settings](/files/MuIOIFQaj7UKoSigxzDC)

## Change the field settings to make link title required field

You can also make the link title field a required field. Follow the instructions below:

1. Go back to the **Manage Fields** page of the **Job Posting** content type.
2. Edit the Link field.
3. Change the Allow link text to “Required”.
4. Save settings.

![Image of new Field settings](/files/B2HeurYOFZKsIIIDben2)

## Re-test it

1. Update your Job posting content page from the previous example and enter the link title.
2. Compare the look of the content page.

The **More information** fields should now be required fields.

![Image of new Field settings](/files/PvV6lapy4YSwJvrxMH55)


---

# 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-8-site-building-exercises/extend-content-types-with-new-fields/exercise-8-1-add-an-external-link-field.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.
