# Forms

* Are very similar to pages and have most of the same features
* However, forms also contain a web form of some kind that can be used to collect information from site users; for example, customer registration form
* Forms workflows and notification processes can be configured for each form

### Form = Page <a href="#form-page" id="form-page"></a>

Fundamentally, each form that you make functions as a page within your site. You’ll recognise most of the content fields on Forms from Pages: `title`, `subtitle`, `background image`, `content` and `feature blocks`. These content fields are used to customise the top matter of your form and work identically to how they work on Pages - in fact, **a Form is literally just a Page with a customisable form attached.**

Remember that Forms are a *webable* entity in Pakk, so once you’ve created your form, you need to mark it as `web enabled` and choose which sites to display it on, as well as configure the meta `title`, `description` and `slug`.

Once you’ve saved your form, you’ll be able to view and copy the URL. Use this URL to link to the form wherever you would use any page URL, e.g.,

* In menus (e.g., aux menu, footer menu)
* In Feature Block call-to-action buttons (e.g., “Register Now” block on homepage)
* Embedded in markdown text (e.g., when writing an article, embed a link to sign up customers)
* In emails
* In direct messaging with customers (e.g., send them directly to a form to capture information)

> There is one noticeable difference between Forms and Pages. Due to the complexity of the UI, Forms are not ‘translatable’ which means you need to create a separate form for each language site you want to display it on.


---

# Agent Instructions: 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:

```
GET https://docs.pakk.io/websites/content/forms.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.