Make the website more beautiful using material-ui

Learn repos should have a LEARN.md file to teach another student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

If your project is very large, consider just teaching a certain tool or implementation that your project utilizes.

Anyone can add his or her profile to the datajson file and get featured on the live project

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

• Add issues of varying difficulty to the repo often.
• Generate issues even if you plan on solving them, so the repository appears as active.
• Contribute/commit often to the repo so it does not go stale.

In order to submit your project into CX you will need at least one issue, but we recommend more so other students have an idea on where to start.

In Community Exchange, GitHub Topics will help the discoverability of your project. You should create topics pertaining to:

• the tech stack you used on the project
• the subject matter of your repo
• the subject(s) covered in your LEARN.md

There is a limit of 20 topics you can add to your repo. There is no need to go overboard with topics. We recommend under 10 topics. You can add topics by following these instructions.

I see some topics already added, I would recommend adding resume and anything you feel will suit based on above instruction.

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

A README is often the first item a visitor will see when visiting your repository. We recommend that your README includes information on:

• What the project does
• Why the project is useful
• How users can get started with the project
• Explain to users that there is a LEARN.md
• Mention your code of conduct
• Who maintains and contributes to the project

You mostly have almost all above items in your Readme already except a few. You could extend it with above list to make it more helpful.

This is Ineligible Repository for HacktoberFest
What is that mean?

Every PR was submitted to a repository that is not participating in Hacktoberfest. Maintainers of the repository can add the "hacktoberfest" topic to their repository if they wish to participate.

Is id key unique? In my opinion, better remove this key.

👋 Hi @Taiwrash ,

I am your GitHub mentor for the GitHub Education, Community Exchange (CX) project. I'll be collaborating with you on preparing your repo for CX.

You mentioned in your submission that you wanted to submit a Learn + Collaborate repo. This means that you would like to teach students, step by step, how to build this project as well as invite other students to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for a Learn + Collaborate CX submission on June 1, 2022.

This issue will serve as a tracking issue to track all issues related to CX. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you

CX Issues

• #117
• #118
• #119
• #120
• #121
• #122

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.

Some suggested prompts/questions you can add to a “Report Bug” template are:

• Briefly describe the bug
• What is the expected behavior?
• Please provide step by step instructions on how to reproduce the bug

Some suggested prompts/questions you can add to a “Feature Request” issue template are:

• Briefly describe your feature request
• What problem is this feature trying to solve?
• How do we know when the feature is complete?

1. The logo in the Hero section should be a little big and the text should be center aligned.
2. The footer looks bad.
3. use read more link in the card description and maybe open a modal on click or enforce a ceratin length for descriptions.

I can work on the styling if you want.