Explore Site »

View Demo · Report Bug · Request Feature

• Learn Git With Commands
• Top 5 Aptitude Test Websites
• Understanding JWT Authentication with Node JS
• Learn DBMS in 5 days

• Make a Pull request -> Before that Read the Guidelines

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

1. Fork the Project
2. Add Your Code
3. Commit your Changes
4. Push to the Branch
5. Open a Pull Request (Guidelines - Write What you have Added ?)

• Don't add Anything
• If you wants to add other code like some Programs or better approach solutions then create one folder and add in it.
• Don't add Programs or other code except html tags and code in Index.html
• Grammatical mistakes aren't considered as that much valid so don't just put that only
• For Hacktoberfest : Don't just make changes of grammer or spaces
• If your Pull Request is not accepted and closed means there's something that needs changes
• If in comment it's written that pull request making conflicts then delete the forked repo and forked it again and make PR again by contributing
• If in comment anything required is written the do that
• See this is Live Deployed Project so need yo maintain it properly
• Add the codes of programming languages inside their folder (i.e python program inside Python Codes) [ Otherwise the PR Won't be merged ]
• Do the required changes and make PR again if your Pull Request is closed without merging.
• Don't add any Paid Content links otherwise it will be your responsibility if the pull request is merged.
• Add Free Online available Material, Don't add any other which is confidential
• You are doing pull requests means you are done the changes and you are the one who is responsible for that code which is added
• Don't make spam pull requests or Issues

Thanks 👍