> For the complete documentation index, see [llms.txt](https://helpdocs.conducttr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocs.conducttr.com/start-here/how-to-use-this-site.md).

# How to use this site

## Structure

Our documentation is organised into several sections:

* Feature Documentation
* How To
* Player Guide
* Concepts
* FAQs

**Feature Documentation** will be your usual "go-to" for how to get something done

**How To** is goal-oriented 

**Player Guide** is for participants

**Concepts** is a section that allows us to discuss features and aspects of Conducttr more deeply so that you have a better understanding of how we think about crisis exercises

**FAQs** addresses frequently asked questions and problems

### Feature Documentation

This and other sections are organised by workflow:

* Planning 
* Designing & Running
* Publishing
* Reporting

## Site key

The cards below reveal a key we're using in our documentation to indicate the type of information on that page.

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td>🔀</td><td><strong>What's right for me?</strong></td><td>An explanation of the choices you have and why you might prefer one over another</td></tr><tr><td>⚡</td><td><strong>Gotchas</strong></td><td>Common things that people forget to consider</td></tr><tr><td>⭐</td><td><strong>Pro-tip</strong></td><td>Our recommendation approach</td></tr><tr><td>🔥</td><td><strong>Pro-users</strong></td><td>Advanced features for pro users</td></tr></tbody></table>


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://helpdocs.conducttr.com/start-here/how-to-use-this-site.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.