> For the complete documentation index, see [llms.txt](https://docs.deepwriter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwriter.com/essential-user-guide/quck-start/wizard-step-1-setup.md).

# Wizard step #1: Setup

To start your generation, enter your project name and author name. These are for internal reference only (visible to you) and won’t influence the generation prompt.

Next, use the slider to set your desired document length. You can select Automatic to let DeepWriter determine the length, or manually set the number of pages. Keep in mind that the final length may vary slightly from your selection.

<figure><img src="/files/fcUwa6KSoFFG3KBdPZTr" alt="" width="563"><figcaption></figcaption></figure>

Finally, choose any advanced options you'd like to include— such as web search, a table of contents, or technical diagrams— based on your specific needs.

{% hint style="info" %}
**Important:** we cover **Web Search** in detail in the [Deep Research](/advanced-strategies/deep-research.md) section.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.deepwriter.com/essential-user-guide/quck-start/wizard-step-1-setup.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.