# Navigation Guidelines

Creating a clear navigation structure is essential for user experience. GitBook provides several ways to organize content.

## Sidebar Best Practices

The left-hand sidebar should follow a logical flow:

1. **Introduction**: Start with a high-level overview.
2. **Getting Started**: Steps for new users.
3. **Deep Dives**: Detailed technical documentation.
4. **Appendices**: Reference material.

## Nested Navigation

Nesting allows you to group sub-topics under a main topic. In `SUMMARY.md`, this is achieved using indentation.

### Example

```markdown
* [Parent Topic](parent.md)
  * [Sub Topic A](sub-a.md)
  * [Sub Topic B](sub-b.md)
```

## Right-Side Sub-Navigation

GitBook automatically generates a "Table of Contents" on the right side of the page based on the headings within that page.

### How to Trigger it

Use `##` and `###` tags to define sub-headers. These will appear as clickable anchor links on the right.


---

# 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/navigation.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.