> 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/understanding-content/fields.md).

# Fields

GovCMS comes with a number of available field types. Each field type has its own limitations and validation options. While we don't cover adding new fields to content types in Introduction to Content Management, it's important to know what fields are available to your website.

<figure><img src="/files/po0PNbbklqUx4fSiHgbf" alt=""><figcaption><p>The various Fields available in GovCMS</p></figcaption></figure>

### Plain text

Standard unformatted text field. Can be either single line like a title, or multi-line like a summary field.

### Formatted text

A multi-line text field with a [WYSIWYG editor](/govcms-content-administration/rich-text-editing-with-ckeditor-5/overview.md). This is used for the majority of text-based content.

### Number

A field that only accepts a number. It can also be configured to hold decimal numbers, as well as have set increments.

### Reference

Reference is used when you need to reference other content inside your website, such as taxonomy terms, or if you want to link two pieces of content together.

### Media

The [media](/govcms-content-administration/media-and-files/working-with-media-and-files.md) field type is used for all media that's uploaded (e.g. images, video, documents) and can even be used to create references to YouTube or Vimeo videos.

### File upload

File upload is a legacy field that should not be used in content types.

### Paragraphs

Paragraphs is the reusable content templates sometimes known as components. While individual paragraphs are configured elsewhere by developers, this field type is how they're added to a content type.

### Select list

A predefined dropdown list of items.

### Date and time

Allows users to select a date, time or date and time. Great for events.

### Address

The address field provides a prebuilt set of fields that can be used for street, state, postcode, etc. It does **not** include the common functionality of an address lookup.

### Boolean

Booleans are simple true/false options.

### Email

Like a the simple text input field, except has an additional validator that ensures the field contains an email address.

### Link

Link can be used for any internal or external link. You can link between content inside your website with a title-based autocomplete search, or link to external websites.

### Meta tags

[Meta tags](/govcms-content-administration/metatags-and-seo/overview.md) are added automatically to all content types. You do not need to add them manually.

### Telephone number

Similar to the email field, this field is a standard text input field, but with validation for phone-number formats.

### Minisite

Minisite allows you to upload a zip file that contains a standalone website, which gets served from your GovCMS website.


---

# 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/understanding-content/fields.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.
