> For the complete documentation index, see [llms.txt](https://docs.formsort.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.formsort.com/adding-questions-and-content/content-reference/next-button.md).
# Next button
The next button, but rendered inline with the content.
This content type can be used when the Next button needs to pulled out of the [layout](/styling/customizing-appearance/content-area-and-form-layout.md#layout-editor), and placed inline with the content of the page. A common use case is "Begin Quiz" or "Start Survey" buttons that are placed above images or text.
If the responder clicks the next button while there are remaining unanswered questions on the current step, they will be scrolled to the first unanswered question, with that question highlighted.
#### Next button settings
You can customize the label of the next button, assign a Question ID, and optionally append a variable value to it. The next button variable returns a Boolean—`true` if the button is clicked, and `false` if it is not.
### Overrides
#### Next button overrides
You can override the overall style and horizontal alignment of the next button in the **style** menu of a next button component.
{% hint style="info" %}
For more detailed instructions on styling options, you can refer to [this section](/styling/customizing-appearance/buttons.md#next-button).
{% endhint %}
#### Step-level overrides
If you would like to use your default next button styling, but would only like to change either the button text or horizontal alignment, you can do so by going to the style tab with the step selected and using the **Next button overrides** option.
---
# 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.formsort.com/adding-questions-and-content/content-reference/next-button.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.
