> 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.md). # Components The Components and Capabilities section explores the core features of Sunbird Spark, showing how learners can access materials on any device while creators easily build and organize engaging courses.


📱 Consumption apps	Web portal and mobile app for learners	Consumption apps
✏️ Asset sourcing & content creation	Tools for creating and managing content	Asset sourcing and content creation
📚 Content collections	Courses, playlists, and digital textbooks	Content collections
🔍 Content discovery	Search and browse for content	Content discovery
👤 User accounts & access	Identity, roles, and RBAC	User accounts and access
🎭 Rich & diverse content	PDF, video, H5P, ECML, and more	Rich and diverse content
❓ Versatile question bank	QuML-based assessments and question sets	Versatile question bank
📊 Reporting & analytics	Built-in admin reports and Obsrv add-on	Reporting and analytics
🎓 Course & batch management	Batches, enrolment, and progress tracking	Course and batch management
🏅 Credentials & certificates	Verifiable certificate issuance	Verifiable credentials and certificates
🎯 Targeted programmes	Observation and project management	Targeted programmes

--- # 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.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 `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.