# Deploying Documentation

In a similar fashion the Javadocs and a Maven site can be deployed:

```bash
mvn site site:deploy
```

## Configuration

First of all include a site configuration:

```markup
<distributionManagement>
   <site>
      <id>site-development</id>
      <name>Project Development Documentation Site</name>
      <!-- The URL should be set externally -->
      <url>${site.develop.url}</url>
   </site>
</distributionManagement>
```

It is a good idea hiding the actual deployment URL, as in some cases it can give too much information. It can be loaded from the settings file during CI.

As with the artifacts deployment we will need some access settings:

```markup
<settings>
   <servers>
      <server>
         <id>site-development</id>
         <username>[username]</username>
         <password>[password]</password>
      </server>
   </servers>
</settings>
```


---

# Agent Instructions: 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:

```
GET https://bernardo.gitbook.io/development-docs-java/maven/deployments/deploying-documentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.