> For the complete documentation index, see [llms.txt](https://docs.coreframework.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coreframework.com/troubleshooting/faqs.md).

# FAQ

Here are some of the most frequently asked questions about Core Framework, which we hopefully can answer here. This list will be updated periodically.

## Licensing

### How do I download?

The only download available is for the WordPress plugin version of Core Framework. Simply login to your account if you have not already, and navigate to [your dashboard](https://coreframework.com/dashboard). There, you will see an option to download the plugin:

<figure><img src="https://949277485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fp10Tm4nYjo9MojbZ6zQt%2Fuploads%2FZ4VFnKG8K5rLnuMfN5Vo%2Fimage.png?alt=media&amp;token=2ab930f4-6610-4f40-af12-af831ef35004" alt=""><figcaption><p>The Dashboard Area on the Core Framework Website </p></figcaption></figure>

### How do I get a license?

The Core Framework web app and WordPress plugin actually requires no license to use. They are free to use and readily available. The only licenses available are for the addons to Core Framework. To get an addon, you can navigate to the [marketplace](https://coreframework.com/marketplace) and choose the addons you'd like to purchase.&#x20;

### What about OxyNinja users?

We made a promise to users of our previous plugin (OxyNinja) that you would receive the Oxygen Integration addon, WooCore, and CoreKit for free. We made a dedicated page for this that you can view here: <https://docs.coreframework.com/getting-started/oxyninja-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 dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coreframework.com/troubleshooting/faqs.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.