Geek Editor is basically an online compiler, somewhat like a codepenn for the following coding languages:-

• C
• C++
• Java
• Python

1. You can write, compile, execute and save code all in one place.
2. You can read other popular codes, and like them.
3. It also allows you to follow other great coders and learn from their code practices.

• ReactJs
• Material UI
• API - Judge0

about- https://rapidapi.com/judge0-official/api/judge0-ce/
documentation- https://ce.judge0.com/

You need npm/yarn installed in your local machine in order to run this app.

npm install
npm start

• Make sure your machine is having internet connection.
• Open shell (which ever your OS support) on your PC.
• Change drive to the location where you want your project to be copied
• Clone it to your local setup by using command git clone <repo link>
• Once cloned, Run the following command in the root directory of the project npm install
• After the process is completed, run the command npm start
• The website will be live on localhost:3000

Comment on the issue. In case of no activity on the issue even after 2 days, the issue will be reassigned. If you have difficulty approaching the issue, feel free to ask on our slack channel.

If you have any queries or suggestions, please use the discord channel of Geek Editor FrontEnd.

Please help us follow the best practice to make it easy for the reviewer as well as the contributor. We want to focus on the code quality more than on managing pull request ethics.

1. People before code: If any of the following rules are violated, the pull-requests must not be rejected. This is to create an easy and joyful onboarding process for new programmers and first-time contributors.
2. Single commit per pull request and name the commit as something meaningful, example: Adding <-your-name-> in students/mentors section.
3. Reference the issue numbers in the commit message if it resolves an open issue. Follow the pattern Fixes #
4. Make a note to add relevent Screen Shots when you make a PR.
5. Pull Request older than 3 days with no response from the contributor shall be marked closed.
6. Do not make PR which is not related to any issues.
7. You can create an issue but you can only solve that particular issue if we approve it.
8. Avoid duplicate PRs, if need be comment on the older PR with the PR number of the follow-up (new PR) and close the obsolete PR yourself.
9. Be polite: Be polite to other community members.
10. PR template should be strictly followed, else the points won’t be reflected on the leaderboard.

happy coding.