> 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/angular-material.md).

# Angular Material

### Info

In the beta version ([**7.0v14\_UI**](https://github.com/Sunbird-Ed/SunbirdEd-portal/tree/7.0v14_UI)) of the Sunbird-Ed portal, we implemented Sunbird Ed Angular Material to enhance the user interface and improve the overall user experience. Despite the availability of several major Angular Material versions, including the latest v16.2.3, we chose to utilize [**version 14**](https://v14.material.angular.io/) for the Sunbird-Ed portal. Here are the key updates:

**Angular Material Integration:**

In Sunbird-Ed portal's beta version (release-7.0.0), we've embraced Angular Material, modernizing the user interface. This integration brings a polished and unified look to our design.

**Theming with Angular Material:**

We've leveraged Angular Material's theming system to customize the portal's appearance, ensuring it can adapt to different branding needs.

**Semantic Components to Material Components Transition:**

To modernize the portal, we've replaced Semantic UI components with Angular Material elements, creating a more consistent user experience.

**Enhanced User Experience:**

The integration of Angular Material, theming capabilities, and component replacement enhances user experience, offering improved consistency, responsiveness, and accessibility.

### Pre-built theme

Angular Material provides four pre-built themes, each showcasing unique color palettes. This simplifies the process of switching between them, as demonstrated by the sample theme screenshots presented below.

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAEDw4QSTF4bOoUHIOEnN%2Fuploads%2FEb4N9j9NeXDFnvqlXD3d%2Ftheme-switch.webp?alt=media&#x26;token=c848a239-3f1c-44bd-84ab-a140d67c91c9" alt=""><figcaption></figcaption></figure>

#### 1. Deep Purple & Amber <a href="#id-1.-deep-purple-and-amber" id="id-1.-deep-purple-and-amber"></a>

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAEDw4QSTF4bOoUHIOEnN%2Fuploads%2FkWzJvfUGBbtxUqBWlR7E%2FDeep%20Purple%20%26%20Amber.webp?alt=media&#x26;token=7d6a75f5-4182-4934-b370-bc88a34410d1" alt=""><figcaption></figcaption></figure>

#### 2. Indigo & Pink <a href="#id-2.-indigo-and-pink" id="id-2.-indigo-and-pink"></a>

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAEDw4QSTF4bOoUHIOEnN%2Fuploads%2FmEjGOk5z6mIRoGGhYUAO%2FIndigo%20%26%20Pink.webp?alt=media&#x26;token=30f41fda-af63-43be-b19c-c1826e8ec9ac" alt=""><figcaption></figcaption></figure>

#### 3. Pink & Blue-grey <a href="#id-3.-pink-and-blue-grey" id="id-3.-pink-and-blue-grey"></a>

<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAEDw4QSTF4bOoUHIOEnN%2Fuploads%2Fa8YecrT3G1Qi2CghD3xF%2FPink%20%26%20Blue-grey.webp?alt=media&#x26;token=e28af712-d0c3-4075-a4bd-9d4b4fa682e6" alt=""><figcaption></figcaption></figure>

#### 4. Purple & Green <a href="#id-4.-purple-and-green" id="id-4.-purple-and-green"></a>

<figure><img src="https://content.gitbook.com/content/h6eC4pApOLA0inzPl7Cw/blobs/KyTqIXR20CNgM2KkHZpc/image.png" alt=""><figcaption></figcaption></figure>


---

# 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/angular-material.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.