> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/questions.md). # Questions ## ⁉️️ What are questions ? Questions allows you to collect information from your respondent and can be built using one or more [answers](/form-management/form-designer/answers.md). Unlike other survey tools on the market you can add any kind of [answer type](/form-management/form-designer/answers/answer-types.md) widgets to your question and mix different [answer types](/form-management/form-designer/answers/answer-types.md) together within the same question. This unique system gives you the best flexibility to create the forms you need. ngSurvey comes out of the box with over +25 pre-configured [question types](/form-management/form-designer/questions/question-types.md) that can be added to your page to collect information from your respondents and fully customized with custom [properties](/form-management/form-designer/questions/question-properties.md) and [answer types](/form-management/form-designer/answers/answer-types.md). {% hint style="warning" %} All changes to survey structure are live changes meaning that if you distributed the survey already to respondent these will see the new changes as well. {% endhint %} --- # 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.ngsurvey.com/form-management/form-designer/questions.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.