> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/use/source-code/ui-user-interface-sunbird-ed-portal/component-style-guide-version-1.md).

# Component Style Guide Version 1

In our project, we've meticulously crafted a style guide that serves as the foundation for the visual and functional aspects of our user interface.

Component style guide encompasses a wide range of components, each designed with a focus on consistency, usability, and aesthetics, similar to Bootstrap's approach. For reference please refer to this below page.\
<https://sunbird-ed.github.io/sunbird-style-guide/dist/#/>

**Benefits:**

This comprehensive style guide ensures a consistent and polished appearance for our project, simplifying the development process and enhancing user satisfaction. It allows for rapid design and development while maintaining a unified visual identity. The naming conventions and structure of the components make them easily accessible and adaptable across the application.

In summary, our project's style guide is a comprehensive framework that encompasses components, a responsive grid system, and a well-defined color palette, all of which contribute to streamlined development, enhanced user experience, and visual consistency.


---

# 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://ed.sunbird.org/use/source-code/ui-user-interface-sunbird-ed-portal/component-style-guide-version-1.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.