> For the complete documentation index, see [llms.txt](https://design.mirakl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://design.mirakl.com/design/patterns/forms.md). # Forms Allow users to submit or edit information. This section describes all design and content rules for forms using Roma. \ Some behaviors remains consistent to every forms such as how to manage backlink or error management. Those are General Guidelines.\ But some behaviors or layout may varies. Take a look to dedicated section "Specific guidelines - Creation vs edition mode". Go to the dedicated section for more information regarding [form components](/design/components/form.md) (e.g. fields, pickers).


Form - Creation		Form - Creation mode	Creation and edition modes Card.png
Form - Edition mode		Form - Edition mode	Forms Card.png
Form - In a modal		Form - In a modal	In a modal Card.png
	Error Management	Error Management	error.svg
Stepper form		Stepper form	Stepper and onboarding stepper Card.png
	Onboarding form	Onboarding form	Capture d’écran 2024-05-23 à 11.26.58.png

--- # 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://design.mirakl.com/design/patterns/forms.md?ask=&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.