> 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 sections:

Section	What's in it	Best for
Feature Documentation	Your usual "go-to" including everything from planning > designing and running > reporting	Designers wanting to get something done
Player Guide	How to navigate the Virtual Desktop	Exercise participants
Concepts	Deeper discussions about features and aspects of Conducttr	You want a better understanding of how we think about crisis exercises
FAQs	Addresses frequently asked questions and problems	Resolving snags
Release Notes	Info about our updates	Keeping up-to-date with Conducttr

### Feature Documentation This and other sections are organised by workflow: * [Planning ](/feature-documentation/planning.md) * [Designing & Running](/feature-documentation/designing-and-running.md) * [Reporting](/feature-documentation/reporting.md) ## Site key The cards below reveal a key we're using in our documentation to indicate the type of information on that page.


🔀	What's right for me?	An explanation of the choices you have and why you might prefer one over another
⚡	Gotchas	Common things that people forget to consider
⭐	Pro-tip	Our recommendation approach
🔥	Pro-users	Advanced features for pro users

--- # 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 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=&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 `automate deployments from our CI pipeline` 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.