> For the complete documentation index, see [llms.txt](https://knowlg.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowlg.sunbird.org/learn/product-and-developer-guide/player/v1/content-import-and-preview-folder-creation.md).

# Content import and preview folder creation

## Offline play

The v1 player is capable to play the content offline locally. Here are the steps to load the content locally:

* Download and extract the ECAR file in a local folder.
* Replace the existing ECAR of the content

  ```
  Got to  => sunbird-content-player/player/public/fixture-stories/custom_eval
  Replace => assets, index.json and widgets folder with extracted files
  ```
* Refresh the page in the local environment.

## Create a preview folder

The v1 player is capable to provide the build to verify the changes locally. Here are the steps to generate the preview folder locally:

* Go to *sunbird-content-player/player*
* Run the following command :- 

  <pre><code><strong>> npm run build-preview
  </strong></code></pre>
* ’The preview folder will create at the following path

  ```
  sunbird-content-player/player/www
  ```
* Just copy and paste it into your project and follow the given [instructions](https://github.com/project-sunbird/sunbird-content-player/tree/release-5.1.0#how-to-render-the-contents)


---

# 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://knowlg.sunbird.org/learn/product-and-developer-guide/player/v1/content-import-and-preview-folder-creation.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.