> For the complete documentation index, see [llms.txt](https://7oroof-themes.gitbook.io/verdikto-wordpress-theme/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://7oroof-themes.gitbook.io/verdikto-wordpress-theme/thank-you.md).
# Thank you!
First, thank you for purchasing our theme!
We would happily welcome feedback from you on how, if anywhere, you would like this documentation improved. If you would find anything a little bit easier and more helpful if we went into more detail, or explained something a little better - we'd be happy to hear it. We want [**Verdikto** ](https://7oroofthemes.com/verdikto/)to be the best theme! If you have any comments, please feel free to email, via my user page contact form or put a ticket at Support Center. Thank you so much!
This guide provides instructions for installation, help on getting started and extensive documentation of features. It is recommended you read it thoroughly to fully leverage the [**Verdikto**](https://7oroofthemes.com/verdikto/) theme's capabilities. Please also make sure to check out our Video Tutorials as they explain everything covered here in greater depth. We hope you enjoy building with [**Verdikto**](https://7oroofthemes.com/verdikto/) as much as we enjoyed developing it and continue to develop with new features!
---
# 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://7oroof-themes.gitbook.io/verdikto-wordpress-theme/thank-you.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 `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.
