# Repository Structure

GitBook allows you to write your documentation in Markdown and host it on GitHub. This page explains how to organize your files so GitBook can interpret them correctly.

## The SUMMARY.md File

The `SUMMARY.md` file is the backbone of your GitBook navigation. It defines the sidebar structure.

### Basic Syntax

A basic link looks like this: `* [Title](path/to/file.md)`

### Grouping with Headings

You can use standard Markdown headings (e.g., `## Heading`) to create sections in the sidebar that are not clickable links but act as labels.

## File Organization

It is best practice to keep related files in folders.

* **Root**: Contains `README.md` and `SUMMARY.md`.
* **Folders**: Used for categories (e.g., `api-reference/`, `guides/`).

### Special Files

* `README.md`: Used as the home page for a folder.
* `.gitbook.yaml`: (Optional) Advanced configuration for sync behavior.


---

# 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://hotwax.adarshraghuwanshi.com/getting-started/structure.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.