> 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/creating-editing-and-archiving-content/adding-field-data.md). # Adding field data As previously mentioned on the [Fields](/govcms-content-administration/understanding-content/fields.md) page, GovCMS supports a number of different field types. Each field can have its own requirements and this can differ between instances. Additionally, GovCMS comes with the Paragraphs module, sometimes called Components. This allows developers or advanced content editors to create repeatable packages of fields that Content Authors can use to create rich and engaging content. ### Fields Each field type has its own **configuration** and **settings**. For example, below is a standard **Textarea field.** The following items have been set in the field configuration: * Its label, 'Body' * A separate, unformatted Summary that can be provided by selecting **Edit summary** * The field is not mandatory * A text format of Rich text has been provided.

Whereas the example below is also a **Textarea field**, however it has a different label, it is mandatory field, it doesn't allow a separate summary and no text format is enabled.

This shows how even technically similar fields can be quite different depending on how your developer has configured them. Another prime example of this is [Taxonomy](/govcms-content-administration/taxonomy/what-is-taxonomy.md) fields. Taxonomy will be covered later, but it's a great example of a single field type that can have **different configuration options** that change how the field is authored and displayed.

Comma separated list, without the ability to dynamically add new terms

Radio list where only one item can be selected

Checkboxes allowing for multiple options to be selected

Autocomplete, with the ability to add new items that are not already present in the list

As there are 16 different field types, with different interfaces depending on configuration options, it would be too exhaustive to document them fully here. {% hint style="info" icon="dumbbell" %} If you're currently doing the GovCMS training, you can add as much test content on your training environment as you like, and by testing out the various content types and paragraphs, you'll be able to experience most of the available field types. {% endhint %} ### Paragraphs / Components **Paragraphs** (cometimes called **Components**) are sets or groups of fields that your developers have created so you can add rich content to your website in a repeatable and consistent manner. You can think of them as small self-contained [content types](/govcms-content-administration/understanding-content/what-are-content-types.md) that are used inside an actual content type. Some examples of Paragraphs on the training environment are: #### Callout

Above is a Paragraph called **Callout**, that contains multiple text fields, a link field and options to configure theme and spacing. This Paragraph allows Content Authors to easily create a Callout and have it display consistently across the website, without having to remember things like what size font the heading text should be, or what styles should be applied to the buttons.

#### Accordion Accordions on the Training website are unique in that they are a **Paragraph with embedded Paragraphs**. In the screenshot below there is a Paragraph called **Accordion**, which includes fields for Expand all, Theme, Vertical spacing and Background. But then it also has a field called Panels, which is a reference to another Paragraph called **Accordion panel**.

This allows Content Authors to create the accordion container and then have as many individual accordion panels as they need. While the creation of new Paragraphs is only covered in the Advanced Content Management training, it's important to notice that even though Paragraphs can be complicated and have additional elements embedded in them, they're all built from the same simple fields. Once you're comfortable with how a text field behaves and how a Rich text editor works, you'll be able to edit any content on your website with ease. --- # 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/creating-editing-and-archiving-content/adding-field-data.md?ask=&goal= ``` `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.