> 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/webforms/creating-a-webform.md).

# Creating a webform

On the **Webform landing** page, select the blue **Add webform** button at the top of the page. This will load a popup and you'll need to provide the following information:

* **Title**: Name of your webform
* **Administrative description**: Optional, this will appear on the **Webform landing** page only
* **Categories**: Optional, this will help you filter the list on the **Webform landing** page
* **Status**: If the form should be open or closed for submissions&#x20;

{% hint style="info" %}
You can keep the Status of your webform Open while developing it, as until it's published no one will know it exists anyway, and search engines will not be able to index it.
{% endhint %}

When you're done, select **Save**.

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

This creates your webform, but it starts as an **empty form** and you need to add specific fields.

Select the **Add element** button. This will provide you with a list of all the different field types you can add to your webform.

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

[The list is very long](/govcms-content-administration/webforms/basic-components.md), so you can use the **Filter by element name** field to search for fields you want to add. We encourage you to try out all the field types to see what kind of data can be captured.

However, for now just add a simple **Text field** by selecting the associated blue **Add element** button.

Elements are configured in a sidebar that's attached to the form view.

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

Each field type has its own fields that are required to configure it. There are too many to cover here, so in the next page we'll cover the **most common** components you can add.

Once a name has been entered you can either select **Save** to just add the element and return to the form, or **Save + Add element** to open the **Add element** popup again to add the next field.

Once you've added a single field, you can click the **View** tab above the **Add element** button to see  what the webform will look like and how it will behave.

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

At this stage, you could send out the URL to the form, and public users could enter their name, select **Submit**, and have that data saved in the GovCMS database.

The only difference between this simple form, and a complicated multi-page census, is the time it takes to add additional 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-content-administration/webforms/creating-a-webform.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.
