# Forms

Build custom, standalone forms beyond your resources for surveys, settings, and bespoke workflows.

- Price: $30/month
- Gem: `gem "avo-forms"`
- Web page: https://avohq.io/addons/forms
- Pricing: https://avohq.io/pricing.md

Not every admin job has a database model behind it. A settings screen, an onboarding survey, a one-off button that kicks off an import: these are forms with logic, not records. With Forms, you build them inside your Avo app and shape each one to the job. Stand a single form on its own page, put several forms on one screen, drop them into the sidebar, or mix layouts however the workflow needs. If you can picture the screen, you can build it.

It runs on the same field DSL you already use on resources. Subclass `Avo::Forms::Core::Form`, declare your fields, then write a `handle` method that runs in the controller with access to `params`, `current_user`, and `flash`. You decide what each submission does.

Group forms into pages that show up in the Avo sidebar, with main pages and nested sub-pages defined through a `navigation` block and no manual route declarations. Scaffold a starting point with `rails generate avo:form` and `rails generate avo:page`. That is a whole standalone-form layer your agent builds on, instead of generating routes, pages, and controllers from scratch in every app.

## See it in action

![Forms overview](https://avohq.io/assets/addons/forms/shot-1-00b93a68d15a785bc4c00c4293ba815aaf77a96f2a90e6b5c3e6770f2f1a74dd.png)

![Forms detail](https://avohq.io/assets/addons/forms/shot-2-00b93a68d15a785bc4c00c4293ba815aaf77a96f2a90e6b5c3e6770f2f1a74dd.png)

## What you get

- Standalone forms with no backing model, subclassed from `Avo::Forms::Core::Form`
- Your choice of layout: one form on its own page, several forms grouped on one screen, or forms placed in the sidebar
- The same field DSL as resources, `field :app_name, as: :text, required: true`
- A `handle` method that runs in the controller, with `params`, `current_user`, `flash`, and `cookies`
- Fields prefilled from their `default:` values, since a form renders as a new view
- Sidebar pages with main pages and nested sub-pages, wired through a `navigation` block
- Generators for both, `rails generate avo:form` and `rails generate avo:page`

## Why it pays off

- Lay out a settings screen, a survey, or a multi-form page exactly how the workflow needs, reusing the field DSL your team already knows, instead of generating forms, controllers, and routes from scratch for each one.
- Dynamic routing and sidebar pages are handled for you, so you write the fields and the `handle` logic, not the plumbing around them.
- Every Avo release makes it better: the form layer keeps working as Avo evolves, and fixes reach your app with bundle update.
- Tokens, time, and focus go to what each form does, not to a forms-and-settings layer built from scratch.

Included in bundles: Growth ($145/month)