An Initiative to help students and professionals get handpicked top-quality global research and industrial opportunities 🎯.

Ignitus runs as a non-profit and works towards the upliftment of education equity worldwide by decentralising research, skill-acquisition, and employment opportunities.

We are creating a global open-source platform where anyone enrolled in an undergraduate/postgraduate program at any institution can look for opportunities, our unique value proposition is we are devoted to educational opportunities with no involvement of any startup, companies, etc. we are still in a phase of creating Ignitus our goal is to act as an opportunity bridge. 🚀

Our only goal is ❝ Skyrocketing a scholar career by providing the best global opportunities ❞. Ignitus platform has got exponential growth after successful Internship opportunities completion by the associated scholars in collaboration with researchers from Stanford Artificial Intelligence Laboratory (SAIL) & Oxford University 🏛.

We are committed to bringing together multiple initiatives for a grand scale open-source product development program for women's in technology. we are honoured to have among us more than admirable leaders in the fight for equal opportunities for women at & .

To know more about Ignitus feel free to browse mentioned resources.

Writings ✏️ that will help you better understand our mission.

• .

• .

• .

Presentations. 🎥

• .

• .

• .

Ignitus is a collective effort by students & researchers from prestigious institutions e.g - Stanford, MIT, UCB, UCLA, USC.

The initiative facilitates people to collaborate and share their knowledge with others by creating short research talks on diverse topics and later own publish their research papers. 📜

It is an ongoing effort and supported through our slack. Anyone can propose a research paper of their interest and form a team to create a talk on it or join an existing team for another paper, you can also propose a paper co-authored by you. Currently, we’re only focusing on computer science conferences.

Once onboard, one goes through a 21-day cycle to collaboratively create the talk in an ad-hoc team, where the members are responsible for designing the structure, flow & content of a 5-minute short talk. The talk is finally published on YouTube 🎥 for a larger audience.

This is your chance to demonstrate your knowledge, impact research, and experience a unique collaborative initiative. 🙌🏻

Why collaborate? 💭

There are thousands of high impact papers, whose findings are not accessible to most of the world. To scale the effort of accessible research knowledge, we got to get together. A high-quality talk creation is a non-trivial endeavour and can be very time-consuming. Through collaboration, we want to change that and scale the process of video production.

A large number of scholars across the world 🌍 can learn from experiences of each and every student & inputs, helping newcomers by answering their queries regarding applying for Master of Science (M.S) program, seeking research opportunities, writing statement of purpose (SOP) etc. 🎓

Who is a talk representative/leader/DRI(directly responsible individual)?

A talk representative/leader/DRI is a person among you, who volunteers to co-lead the talk building effort. As a DRI, you will often be the person of contact for us. Your responsibilities may include: coordinating people and the process, improving, and synthesising the content - you will be credited and acknowledged for your substantial contribution.

Who are behind this program?

We have come a long way from humble beginnings, we now have 1400+ scholars 👨‍🎓 👩‍🎓researchers who have actively volunteered to be a part of our organisation. we aim to serve a larger student community in the future.

Can I propose a paper co-authored by me?

Sure, if your paper gains interest within the community, you can start working on creating a talk on it. It's a great way to spread your research and produce high-quality talk.

What is the prerequisite in order to contribute to the program?

Please apply only if you’re passionate about research, collaborative in nature and willing to commit your time. Though no specific skill set is required, applicants are expected to have some level of expertise in the area of paper for which talk is being created.

To participate in the program, you must be 18 years of age or above. You can be a student, a professional or an enthusiast. You can come from any part of the world 🌍.

Welcome the sky is the limit.

How can I apply?

Please visit our .

Project's Requirements

In the beginning we don't expect much from selected candidates as we will be there to help them learn technologies that we are making use of at Ignitus, but it would be great if you have an background in react.js & a motivation to learn new things and implement some cool stuff as well.

❝ Let’s grow together - share your knowledge, we will share ours! ❞

Technical Requirements 🎯

• Experience with react.js, some knowledge of redux.js & TypeScript will be helpful.

• Experience in writing Html/Css.

• Experience with distributed version-control system e.g - git.

Just to make sure you are comfortable with our legacy code-base, feel free to pick up some easy tickets.

Tasks & Features.

We have a lot of migration stuff that needs to be work on, here are a list of migration-related tickets.

Migration Tickets

1. Migration to styled components(Emotion).

2. Removal of Bootstrap 4 => Pure CSS.

3. Pure CSS => Styled components.

Feature Tickets

1. Career page Implementation.

2. Job description page Implementation.

3. Job confirmation page Implementation.

Ideally, Initially you should start with the migration issues in client/server-side architecture, then we you move ahead with feature tickets. In the end we plan to Implement mentioned modules.

Careers, Profile, Opportunities, Messages, Settings, along with the migration to emotion, react-hooks, and Typescript.

Final Thoughts 💭

Don't worry about the complexity of the tasks, we will be there to answer your questions, let's learn and grow together in this journey. we are open to new ideas and suggestions from your end as well and if they make sense, we can change the requirements & scope of the project accordingly and based on your experience you can help us either on the client/server-side.

Best of luck 🍀🧧

IDEA: Ignitus client & API documentation. 🚀

Let's start with Client documentation, Welcome to the Ignitus Design System – an open-source library of React components for creating features @ignitus. It was originally created to help our teams work faster together, but it can be easily adapted to create applications with the look and feel of your own experience.

Why we created a design system?

We created this Design System with several goals in mind:

• To document components, patterns, and design guidelines, all in one place.

• To ensure consistency in our code and design.

• To standardise the visual language and experience of our products.

Why should we document it?

• We perceived that newcomers find it difficult to understand the workflow of existing UI components in turn difficulty in contributing to projects.

• Contributors work in different ways & styles, they work with different tools and they all work at different levels of maturity in turn ended up with their own implementation.

• Documenting it will not only be helpful to newcomers but may also encourage the adoption of our design system.

It is a collection of React UI components for quickly building user interfaces at our organisation, sooner we plan to publish it as an NPM Package as well. 🍻

You should check out our, which contains list of components unfortunately. At the moment, we are missing insightful documentation for our library.

Now let's move to API documentation.

The main objective is to document API in such a way that it would be easily understandable to new and existing contributors. As we believe a well-documented API and usage/ use-case document can assist in overcoming the bottleneck of trying out the APIs.

What we are looking in terms of API documentation?

• A use-case of the API, with some conceptual definition indicating what purpose a particular api call serves.

• A use-case of the API, depicting payload structure sent by the client.

• A use-case of the API, depicting required/optional properties sent by the client.

That's all we want to accomplish with Google season of Docs 😃.

Project summary

Difficulty Level:

Moderate

Expected Outcome:

• We would be delighted to have understandable & simple human-friendly documentation enhancing design system experiences of our users.

• It would be great if almost all the resources served by our API are documented.

• It would be great if API & Design System docs should be easily understandable by contributors.

Required Skills/knowledge:‌

• Experience with technical writing.

• Brief knowledge of languages, frameworks etc used at Ignitus.

• Motivation & Enthusiasm towards our mission at Ignitus.

Admins:

&

Mentors:

&

Note: Feel free to contact us on if you have any Questions :)

Contributing to Ignitus.

We especially welcome contributions from people from groups underrepresented in free and open source software! 🏳️‍🌈.Our community aspires to be a respectful place, before proceeding please read and abide by our Code of Conduct.

How to create a pull request ?

Steps to follow before opening a pull request.

• Please follow the to create a pull request.

• Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (Check for more info)

• Create a new branch for the ticket you are willing to work on, rather than working directly on master

Steps to follow after opening a pull request.

• Check the travis-ci continuous integration build once it completes. This usually takes about 10 minutes ⏱, and if any tests fail you can find details in the build log.

• If somehow build fails / not passing then:

  • Try to fix whatever caused it to fail if you can.

Do, we have to follow any code conventions?

Yes, you do please refer to 📜.

Do, we have to write unit tests for every new feature we add?

Ideally, pull requests should include new tests for any new features, as well, but it is an optional requirement.

Do, we have our own design system?

We do, to keep our designs consistent, we have created UI kit that contain many of our commonly used styles. , please use buttons, typography, colors, navigation components etc. defined in the design-kit. if you are building a whole new section, try to divide that into atoms, molecules, etc and add them in the design kit and use it from there.

Getting Started

What are the prerequisites ?

The source code of Ignitus is separated into a several directories , mostly following easy to understand separation conventions.

Here is the brief overview of source code directory structure.

(Excerpt from Google's )

The goal of Season of Docs is to provide a framework for technical writers and open source projects to work together towards the common goal of improving an open source project's documentation.

Let's bring open source and technical writer communities together, to the benefit of both. Together we raise awareness of open source, of docs, and of technical writing.

For further information on GSOD please refer its . 📒

GIT convention.

• Please don't commit your package-lock.json until & unless you are not adding a new package.

• Please create a new feature branch from develop not from master, and also create a pull request to develop not to master.

Naming convention.

• Use camelCase for defining variable as const, let.

• Use camelCase for className.

Iconography convention.

• Use SVG Icons defined in ignitus-Icons, if you don't find the icon you want to use download its SVG from font-awesome/Material-icons, please don't forget to give them credits by leaving a comment in the file.

• Only use the Material Rounded Icons and don't add from any other outside websites. In case, you do not find that icon in the list, please ask the maintainer.

Types convention.

• Please name Types in PascalCase. e.g - TeamItemProps is written in PascalCase.

• Do not export types or functions unless you need to share it across multiple components.

Directory Structure convention. 📁

Strings convention.

• Use 'single quotes' for strings.

ES6 convention.

• Use arrow functions => over anonymous function expressions.

• Always surround loop and conditional bodies with curly braces.

Readability & Formatting convention.

• Please move all relative imports after absolute imports.

• Please don't use IDS in html tags.

Error

• If you get any err similarly to this Node SASS could not find a binding for your current environment, try switching node version to v8.16.2.

Design team

Ignitus design is a loose, informal team that works on the design of the user experience and developer experiences. The primary areas of work are web application design, visual theme, and icons. Resources for each of these areas can be found in the Github repo.

The main person managing the designs is Paarmita Bhargava. The best way to contact the team is through the #design on slack.

We use slack to communicate on smaller issues, talk about what to work on next, and just general chatter. It’s good to get to know the other people and for the organization in general.

Design guidelines

The simplest way to contribute to ignitus design is to submit bugs, enhancement requests, see if design breaks UX principles or guidelines. You can create an in Github to do so.

The process to do so is the following:

• First, discuss the idea with the team on the channel.

• Once all agree on the decision, proceed with opening an issue in the so that it's not forgotten and be tracked.

• You can start with cloning the

We support all users from beginners to experts

We believe that in a non-profit community everybody is welcomed. We have a task for everyone interested to join. We stay with users every step of the way to help them learn fast as a beginner and then become an expert over time.

We're building one product, together

We're highly focused on ensuring that no matter how big our product gets, the entire experience stays cohesive, consistent, and interconnected.

Tools

, or pencil & paper for wireframes.

Figma: for designs

Familiarizing oneself with the Figma tools and features. allows you to design and prototype together, in real-time and in one place.

To join the design team, ping in on slack. As it is a non-profit organization, so we are on the Figma free plan and can only provide view-only access.

We are many working on the Design system, Web app, and Landing Page pages in the Figma project.

How to communicate with us?

All communication should happen on Slack, GitHub.

What is the deadline for any task submission?

Ideally be active and complete your tasks within the appropriate duration. ⏱

What is the Technical stack for this project?

Please refer .

How to start as a beginner so as to contribute to the project?

There are many beginner level issues to begin with which includes documentation 📄, development & design. Also, feel free to open new tickets, contributors can claim a ticket by commenting on it. We are always open to new ideas and suggestions.

UX Design process

Who are the users?

The users of this platform will be researchers, scholars, students, and professors from all over the world, whose goal is to work on a research project collaboratively. They will work in groups and communicate through a messaging feature.

Here are some of the tools that we use @Ignitus to manage our day-to-day workflow. ☸

JIRA

It is a tool developed by Atlassian. It is used for bug tracking, issue tracking, and project management.

Feel free to join us by clicking on the .

We are currently working on building the design system for our web application. Please have a look at Ignitus Figma project to have a look at our progress.

Color palette

The central principle of visual design in this app is the cleanness of user interface and the emphasis on the main elements of the content. Based on that was built look and feel of the app. For this purpose colors were defined as bold and engaging which can attract attention to an element even if it takes a small part on the screen. We also didn't want to confine our look into a limited choice of colors so it was decided to use many different shades for additional colors.

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

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.

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 icons for the platform.