> For the complete documentation index, see [llms.txt](https://docs.3techagency.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3techagency.com/documentation/workflows/build-pages-and-forms.md).

# Build pages and forms

Build landing pages with Elementor or the block editor, apply your brand, and add a working contact form.

## Choose the editor

Tell Chat which editor to use.

| Editor                                      | What the assistant can do                                                                                                                                  |
| ------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Block editor (Gutenberg)                    | Build and edit pages. Block packs such as Kadence Blocks, Spectra, GenerateBlocks, Stackable, Otter and Essential Blocks are used when active and enabled. |
| Elementor                                   | Build and edit pages, widgets, global colors, fonts and classes. Needs Elementor active and an Elementor document.                                         |
| Beaver Builder, SiteOrigin, WPBakery, Brizy | Depends on the adapter. Cards marked **Read only** can be inspected; make layout changes in the native editor.                                             |

Check **Integrations > Page builders** before asking for a layout edit.

## Build a landing page

1. Choose **Build a landing page** (Guided; Elementor) or ask Chat "Build a landing page in the block editor".
2. Give the offer, audience, primary call to action and where it should link. Your Brand Kit supplies voice, colors and fonts.
3. Review the proposed section outline.
4. The page is built as a **draft**. Whole-page builds and redesigns of an existing page go through the **Draft Sandbox**, so the live page is never the working copy.
5. Preview desktop and mobile. Check links, text, images, forms and SEO fields.
6. Choose **Review and publish**. A large page may ask you to **Back up and continue** first. If the live page changed since the copy was made, you are warned before publishing.

Publishing a sandbox draft copies only the page-builder data across, so SEO fields and other plugins' data on the live page are kept. Products cannot be forked into the sandbox.

## Apply your brand colors and fonts

**Apply my brand colors and fonts** (Guided; Elementor) writes your Brand Kit to the Elementor active kit. You can also use **Apply to Elementor active kit** in Site Knowledge > Brand Kit. Review what will change first. Undo from History.

## Create a contact page with a working form

Supported form plugins: **Contact Form 7**, **WPForms**, **Gravity Forms** (separately licensed), **Fluent Forms** and **MetForm**.

{% stepper %}
{% step %}

### Start

Choose **Create a contact form** (Guided) or ask "Create a contact form with name, email, phone and message, and add it to my Contact page". The assistant lists the active form plugins.
{% endstep %}

{% step %}

### Confirm the fields

Name, email and message, with phone optional. Set where submissions go in the form plugin.
{% endstep %}

{% step %}

### Create or reuse a form

The assistant reuses a suitable form or creates one through the active plugin.
{% endstep %}

{% step %}

### Place it on a draft page

It is embedded with a supported block or builder widget on a **draft** Contact page.
{% endstep %}

{% step %}

### Test before publishing

Preview, submit a test entry, check delivery and spam handling, and add consent or privacy text.
{% endstep %}
{% endstepper %}

With no supported form plugin active, the assistant shows a Requirement card and does not claim a form exists. It never invents a shortcode or installs a plugin without your click. Integrations offers a free install candidate where one exists.

## Custom fields

ACF, Meta Box, Pods and JetEngine fields can be read and written when the plugin is active. Free ACF is the install candidate. Test one write on a draft before a bulk edit.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.3techagency.com/documentation/workflows/build-pages-and-forms.md?ask=<question>&goal=<user_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 `automate deployments from our CI pipeline` 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.