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