# Identity & Guidelines

### **Defining our brand**

#### Who we are?

**Our mission** is to bridge the gap between professor, students, researchers and scholars, by connecting them.

**Our vision** is to help research oriented people and help in boosting their resumes by providing opportunities.

### **Brand values**

Helpful, Understand, Trustworthy

### **Voice and Tone** 

* Conversational 
* Passionate
* Enthusiastic
* Intelligent
* Friendly
* Helpful

### **Design elements**

The logo is composed of 2 elements- leaves and trunk. The logo symbolizes joining hands to form a community (in form of a tree trunk) and as it is a non-profit community so representing that in the form of a tree. From the name "Ignitus", the leaves can be looked in the form of flames to represent the passion and desire to help people.

The symbol is legible at most sizes, and a small version is provided for micro applications. 

### **Logo**

#### Usage on backgrounds 

The full-color logos should be used only on white, black, grey or navy blue backgrounds. Avoid using full-color logos on photographs unless the logo sits on a black or white area of the image.

![](/files/-M7bA0dV5z6IORV44sIc)

#### **Colors**

Gathering the insights about the education platform we decided to choose a Navy Blue color. Indeed blue is associated with open spaces, freedom, trust, loyalty, sincerity. 

#### **Typography**

Based on our mission and vision**,** we wanted to find a font expressing a friendly and human feeling. so choosing American Typewriter.

#### **Icons**

To have a friendly feeling, I used the [Rounded Material Design](https://material.io/resources/icons/?style=round) icons for the platform.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ignitus-docs.gitbook.io/ignitus/design/brand-identity-and-guidelines.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.