> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dforms/getting-started.md).
# Getting Started
Everything you need to go from signing in to your first published form: sign in with your Dapta account, build and publish a form in five minutes, and learn your way around the dashboard.
Start here if you are new to dForms. Three short pages take you from the sign-in screen to a live form and a dashboard you know your way around.
The Forms page is where every form you build lives, grouped in folders if you like. Create form starts a new one.
1. [**Sign in with your Dapta account**](/dforms/getting-started/sign-in.md): open app.dforms.ai, click **Continue with Dapta**, and land in your workspace. Same login as app.dapta.ai.
2. [**Quickstart: your first form in 5 minutes**](/dforms/getting-started/quickstart-first-form.md): create a form, add three questions, preview it on mobile, publish it and copy the public link.
3. [**Dashboard tour**](/dforms/getting-started/dashboard-tour.md): Home, the left menu, the forms list with its folders and search, the profile menu, the app and workspace switchers, the theme toggle, and how to collapse the sidebar.
> **💡 Tip:** dForms is free and has no plans or limits to unlock. The only thing you need is a Dapta account.
---
# 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.dapta.ai/dforms/getting-started.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.
