> For the complete documentation index, see [llms.txt](https://sunbird.gitbook.io/sunbird-spark/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sunbird.gitbook.io/sunbird-spark/learn/components/rich-and-diverse-content.md).

# Rich and diverse content

Spark supports a wide range of content formats, so learners get the right experience for each content type.

| Format             | Description                                         | Player                          |
| ------------------ | --------------------------------------------------- | ------------------------------- |
| PDF                | Document content                                    | PDF Player (V2 web component)   |
| Video              | `MP4`, `WebM` — adaptive streaming optional         | Video Player (V2 web component) |
| H5P                | Interactive HTML5 content                           | H5P Player (V2 web component)   |
| EPUB               | E-book format                                       | EPUB Player (V2 web component)  |
| Interactive (ECML) | Rich interactive content built with the ECML editor | ECML Player (V2 web component)  |
| Audio              | `MP3` and other audio formats                       | Audio Player (V2 web component) |

All players are V2 web components. They can be embedded in any web application, not just the Spark portal. This lets adopters build custom learner-facing applications while reusing Spark's content players.

{% hint style="info" %}
**For developers:** `ECML` is the format name used in developer documentation and APIs. In the learner-facing portal UI, ECML content is shown as **Interactive**.
{% endhint %}


---

# 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://sunbird.gitbook.io/sunbird-spark/learn/components/rich-and-diverse-content.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.