> For the complete documentation index, see [llms.txt](https://seyarat.gitbook.io/seyarat-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seyarat.gitbook.io/seyarat-docs/installation/step-1-download-theme.md).

# Step 1 - Download Theme

#### Downloading Seyarat Theme Files From ThemeForest

If this is your first time downloading Seyarat from ThemeForest, we recommend choosing the **All Files & Documentation** package, which includes the theme files, child theme, documentation, and other included resources.

**Step 1** – Log in to your ThemeForest account, go to the **Downloads** page, and locate your Seyarat purchase.

**Step 2** – Click the **Download** button and choose one of the following options:

* **Installable WordPress file only** – Contains only the theme ZIP file for WordPress installation.
* **All Files & Documentation** – Contains the complete Seyarat package, including additional files and documentation.

<p align="center"><img src="https://1137831851-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnWlIbC5CXBAhb9rMlflt%2Fuploads%2FO3J7PquRFBjUKaxVlGPa%2Fdl.avif?alt=media&amp;token=5ad066d8-c855-4861-b387-8cf3515c83e9" alt="" data-size="original"></p>


---

# 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://seyarat.gitbook.io/seyarat-docs/installation/step-1-download-theme.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 `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.